postgressomethi

24 ms·

1.
by postgressomethi 2y ago
I always thought there should be a two-arg overload of new, so you could write new(bool, true) or new(int, 20). Would solve the problem without any trickery.
2.
by postgressomethi 2y ago
A Nintendo Switch is a non-hardware decryption system?
3.
by postgressomethi 2y ago
Could "effectively controls access" be attacked here? The purpose of the hardware is not to control access.
4.
by postgressomethi 2y ago
> You might think adding a UNIQUE index would cause the "losing" xact to get constraint errors, but instead both xacts succeed and no longer have a race condition. This is not true. What happens is that the (sub)transaction th
5.
by postgressomethi 3y ago
> Imagine booting your computer and having to give an email to login offline. As much as I hate what modern Windows has become, this is not actually true. If you know the correct sequence of clicks you can avoid this. Not defending thi
6.
by postgressomethi 3y ago
Ah, now I see I responded to the wrong message.
7.
by postgressomethi 3y ago
I'm sorry, I wasn't being clear. Any column meaning "this row is to be ignored for most applications" is an annoying pattern.
8.
by postgressomethi 3y ago
While that's kind of convenient in a lot of ways, it also makes querying the database really annoying, since you have to remember to add the filtering to every single query or you're screwed. Personally, I wish there was a databa
9.
by postgressomethi 3y ago
Sequences kind of have the same issue, because you don't know if a gap is because of a rollback or an uncommitted transaction. Though with some logic you can do a pretty good job at this with sequences. And then you're not in th
10.
by postgressomethi 3y ago
Polling an updated_at column is not robust in its most simple form, as transactions are not guaranteed to commit in that order.
11.
by postgressomethi 5y ago
No.
12.
by postgressomethi 5y ago
That's still, in my opinion, overkill and unnecessary.
13.
by postgressomethi 5y ago
> Adding a column, changing column's nullability and adding/changing constraints is already zero-downtime in PG. Making a previously nullable column NOT NULL is not zero downtime. Neither are adding constraints -- except in so
14.
by postgressomethi 5y ago
I don't like really solutions which force everything into a single schema just to do migrations. They shouldn't be that difficult. In this particular case, rather than making everything a view all the time, you could just use vie
15.
by postgressomethi 5y ago
> This approach doesn’t work for LISTEN because typically a client will listen for its entire lifecycle so you can’t share connections in a pool. But you only need one connection for LISTEN per database, total. So I'm confused why
16.
by postgressomethi 5y ago
Can this quote die already? Rob has repeatedly demonstrated he doesn't know what's best for everyone.
17.
by postgressomethi 5y ago
> LISTEN ties up one connection completely I've seen this twice in this thread, but I don't know what that means. Can you explain a bit?
18.
by postgressomethi 5y ago
Huh? The VPN isn't for privacy.
19.
by postgressomethi 5y ago
> Unless you edit pg_ident.conf, your postgres install will not listen for connections outside of on localhost. I don't know what the defaults are, but pg_ident.conf has absolutely nothing to do with this. The main configuration fi