I have no practical experience yet, but i evaluated the market for a password sharing solution for a team with similar requirements within an enterprise.
It uses a public/private key approach, where the plain passwords never leave the local machine and shared passwords are re-encrypted with each users public key.
I have been using Insomnia for a few years now but was blown away when a colleague told me i could right click the send button and get some additional features... Crazy UI anti pattern. There is no hint that this button has a secondary functionality.
I usually do that as well. But sometimes the properties of a product are not maintained correctly and you might miss out on certain manufacturers completely. Last time this happened to me was when looking for a new TV. Sony was completely filtered out although some of their TVs had all the features i was looking for.
TLDR: The (wrong) filter settings might make you blind for the whole range of the market.
I once had a similar situation with the question "Is everything OK?", which is slightly different from "How are you?".
I am a German living in Germany and i once caused a car crash that made another car spin into the ditch on the side of the road. That car was driven by a family of Russian heritage.
After getting out of the car i spoke to the other parties wife first and I asked "Is everything OK?" with what i ment: "Is there something very wrong beyond the things that are obviously wrong. Like, is your child bleeding to death or is it only the car damage."
But the woman did not understand it this way at all and was a little bit furious because to her obviously nothing was OK.
Of course she had every reason to be upset, but the likelihood of a German interpreting my question in a rude way would have been way lower.
To get production EXPLAINS for problematic queries you can activate auto_explain on a postgres instance. For my transactional system i have set it up to log EXPLAINS for all queries that take more than 2000 ms.
Auto_explain is a pretty great tool to spread knowledge on yea - I've actually built out a lot of functionality related to our DB handle where I work and one of the features I added was a software configuration to establish a threshold that could also be impacted by other runtime variables. We've used this to track specific classes of queries over time and figure out what's going wrong and it can be advantageous (if you know a query sometimes does run long) to capture explains of it executing quickly - sometimes you'll get really helpful information like the query planner changing it's mind when passing a threshold of so many rows and know clearly what you want the query planner to decide to do.
If you're a small enough shop to consider it I highly recommend setting up something to automatically explain queries meeting some criteria on production or using some analysis stack (like new relic) to just capture all the query executions within certain time windows.
These tools all come with costs and should never just run continuously on production if you're getting no benefit from them, but the value can be quite significant.
Great extension, yes. There is overhead when enabling the timing and buffers options, but sometimes it's not big [1]
But auto_explain solves only part of the task – you can see what happened, but cannot see the answers to "what if" questions. ("What if I used this index?")
It's good to auto explain but I would also add that going in and running explain (analyze, buffers) is really beneficial to seeing how much the query uses buffers and how many pages it has to load from disk.
This looks very interesting. I had real difficulty where I needed both a btree and gin(pg_trgm) index on the same column. When using `like` postgres would consistently choose the btree index which resulted in performance that was something like 15secs as opposed to the 200ms or so I'd see if the gin index were used. In the end I added two separate columns, one for each index so that I could force the correct one to be used for a particular query.
Another example for keyword matching: I work on a German/Polish team. We sent money for a birthday present from Germany to Poland. Someone used the colleagues' nickname "Kuba" in the subject line. The Paypal account of the Polish colleague was blocked afterwards. But he could resolve the issue via support afaik.
I'd wonder why the US is still embargoing Cuba after all these years. What's the endgame? What's the goal? The Cuban regime is still there and the Soviets are long gone. It seems petty and spiteful.
Letting Cuba off the hook would require politicians to admit they are wrong and have been for decades. In contrast, keeping the sanctions up does not cost the government much and companies have long factored in the sanctions/compliance as cost of doing business, so there is no pressure on politics from that side.
Like most things in America it comes down to political pandering thanks to the two party system. You may have noticed a lot of progress or corruption on the Cuba front in recent memory based on your political affiliation. There is a large “Cuban” American population that primarily hates the regime in control of Cuba and will support the political opponent that is speaking tough on Cuba. Whether you care about Soviet’s or Communism or revenge is irrelevant because what you do care about is south Florida and South Florida still cares deeply.
Just to augment the story: Kuba is not an internet nickname.
It is a shorter form of given name Jakub (Jacob).
I use Jakub only in documents and during formal events.
For everyone else I'm Kuba.
The community edition is updated more often than i would like and sometimes features break but bugs get fixed quickly and they add usefull stuff all the time.
Dont know what i would do if i was stuck with pgAdmin...
I'm using it on daily basis but it's not a smooth experience. I'm not sure if it's just me that very time I switch to a new database in dbeaver and start running a different query ... more often than not it's just stuck there for more than half min and eventually told me it's not connected to the new database yet so I had to refresh the connection. For all the SQL tools I've used, dbeaver takes the the longest to realize it's actually not connected to a db. It's not fun.
As someone who likes Postico but has some frustrations with it, I've been considering giving TablePlus a try. Can you describe some of the ways TablePlus falls short compared to Postico?
it seems the guy releasing nightly builds even don't have permission to merge. I don't know why no one folk and release a fix version with active members
Years ago I followed a guide I found online [0] which involves renaming the "Reboot" scheduled task file and creating a folder with the same name in its location, so that the OS fails to re-create the task file. Haven't had an unexpected reboot since.
This technique was familiar to me from the Kindle jailbreaking scene, in which creating a directory with a certain path would cause the Kindle's auto-updater to error out when it tried to `rm` what it saw as a preexisting partially-downloaded update file (the Kindle's OS is Linux-based, so the file-delete operation fails on a directory).
Another option in that area is https://www.passbolt.com/
It uses a public/private key approach, where the plain passwords never leave the local machine and shared passwords are re-encrypted with each users public key.