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.
A Nintendo Switch is a non-hardware decryption system?
Could "effectively controls access" be attacked here? The purpose of the hardware is not to control access.
> 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…
> 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.…
Ah, now I see I responded to the wrong message.
I'm sorry, I wasn't being clear. Any column meaning "this row is to be ignored for most applications" is an annoying pattern.
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…
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…
Polling an updated_at column is not robust in its most simple form, as transactions are not guaranteed to commit in that order.
No.
That's still, in my opinion, overkill and unnecessary.
> 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 --…
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…
> 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…
Can this quote die already? Rob has repeatedly demonstrated he doesn't know what's best for everyone.
> 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?
Huh? The VPN isn't for privacy.
> 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…
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.
A Nintendo Switch is a non-hardware decryption system?
Could "effectively controls access" be attacked here? The purpose of the hardware is not to control access.
> 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…
> 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.…
Ah, now I see I responded to the wrong message.
I'm sorry, I wasn't being clear. Any column meaning "this row is to be ignored for most applications" is an annoying pattern.
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…
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…
Polling an updated_at column is not robust in its most simple form, as transactions are not guaranteed to commit in that order.
No.
That's still, in my opinion, overkill and unnecessary.
> 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 --…
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…
> 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…
Can this quote die already? Rob has repeatedly demonstrated he doesn't know what's best for everyone.
> 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?
Huh? The VPN isn't for privacy.
> 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…