Viewing profile — petereisentraut

The problem with this and similar requests is that it would change the identifier scoping in incompatible ways and therefore potentially break a lot of existing SQL code.

The working group also discussed ORDER BY ALL, but for some reason most participants really did not like it.

This was also discussed at the last SQL WG meeting but was postponed for further refinement. But it’s likely to be added soon.

Git 2.38.0 is the version where git archive uses an internal gzip implementation instead of calling the actual external gzip. This internal implementation has two improvements for …

The configure generated from configure.ac has always been checked into Git for PostgreSQL. So with either the old or the new make dist approach, the configure in the tarball matche…

> - Support for deferring NOT NULL and CHECK constraints to the end of a transaction (just ran into this problem yesterday) I'm curious what the use case of this is? Deferrable con…

> Care to explain why you think NULLS DISTINCT is the "right" default behavior? What problems does it solve to warrant additional complexity by default? It's the most consistent wi…

I am the author of this feature. The background here is that the SQL standard was ambiguous about which of the two ways an implementation should behave. So in the upcoming SQL:202x…

It's a bit more complicated than that. You will also notice another release note item in PG13 that says "Allow inserts, not only updates and deletes, to trigger vacuuming activity …

Sure they can. See example here: https://www.postgresql.org/docs/current/plpgsql-transactions...

This is also much faster than the equivalent using a PL/pgSQL trigger.

A snapshot is actually just a struct with a few transaction IDs (xids) and some other bookkeeping that describes which slice of the physically stored data is supposed to be visible…

Caps Lock is already mapped to Control.

The problem with this is that time zone definitions change, both in the future because of political and administrative changes, as well as in the past, when mistakes are corrected.…

Right. It will probably be enabled by default in PostgreSQL 12.

You also cannot run VACUUM inside a DO block. It's the same thing underneath.

Now is the time to test this. From my early experiments, you can expect to get speedups for queries that last longer than a few seconds. A lot depends on whether I/O, caching, etc.…

Feature author here. Running not-allowed-in-transaction-block DDL, such as VACUUM, still won't work in stored procedures. Room for future improvement.

The release notes say Amit Khandekar. (I don't know him.)

Try OmniDB perhaps? (disclaimer: my employer (but open source))

Another problem is that the bool provided by stdbool.h is 4 bytes on some platforms, which breaks PostgreSQL all over the place.

It has to do with how the tuple header that stores the metadata is designed. See comments here: https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f...