petereisentraut

6 ms·

1.
by petereisentraut 11mo ago
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.
2.
by petereisentraut 11mo ago
The working group also discussed ORDER BY ALL, but for some reason most participants really did not like it.
3.
by petereisentraut 11mo ago
This was also discussed at the last SQL WG meeting but was postponed for further refinement. But it’s likely to be added soon.
4.
Will Postgres development rely on mailing lists forever?(vondra.me)
5 points by petereisentraut 2y ago|0 comments
5.
by petereisentraut 2y ago
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 this purpose: First, it doesn't store the timestamp.
6.
by petereisentraut 2y ago
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 matches the one checked into the source code repository. So this
7.
by petereisentraut 3y ago
> - 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 constraints are usually considered for foreign keys, si
8.
by petereisentraut 4y ago
> 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 with the equality behavior of null values el
9.
by petereisentraut 4y ago
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, this was addressed by making the behavior implementation
10.
by petereisentraut 6y ago
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 in autovacuum", which is because vacuum is no
11.
by petereisentraut 6y ago
Sure they can. See example here: https://www.postgresql.org/docs/current/plpgsql-transactions...
12.
by petereisentraut 7y ago
This is also much faster than the equivalent using a PL/pgSQL trigger.
13.
by petereisentraut 7y ago
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 to a transaction. The article shows the details of that.
14.
by petereisentraut 7y ago
Caps Lock is already mapped to Control.
15.
by petereisentraut 8y ago
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. So a datum like "1st of May 2022 6pm in London"
16.
by petereisentraut 8y ago
Right. It will probably be enabled by default in PostgreSQL 12.
17.
by petereisentraut 8y ago
You also cannot run VACUUM inside a DO block. It's the same thing underneath.
18.
by petereisentraut 8y ago
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. dominates. The only disadvantage is that it takes t
19.
by petereisentraut 8y ago
Feature author here. Running not-allowed-in-transaction-block DDL, such as VACUUM, still won't work in stored procedures. Room for future improvement.
20.
by petereisentraut 8y ago
The release notes say Amit Khandekar. (I don't know him.)
21.
PostgreSQL's handling of fsync() errors is unsafe and risks data loss(postgresql.org)
4 points by petereisentraut 9y ago|0 comments
22.
by petereisentraut 9y ago
Try OmniDB perhaps? (disclaimer: my employer (but open source))
23.
by petereisentraut 9y ago
Another problem is that the bool provided by stdbool.h is 4 bytes on some platforms, which breaks PostgreSQL all over the place.
24.
by petereisentraut 9y ago
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...
25.
by petereisentraut 9y ago
Any XML document that you can address via XPath in a sensible way. If your XML document is a mess, you'll only be able to get out a mess. :) To get XML from a table, functions already existed in previous releases (XMLELEMENT etc.).
26.
by petereisentraut 9y ago
Not a priority for 2Q at the moment. Still general interest in the community, but hard to predict right now.
27.
by petereisentraut 9y ago
Several reasons: - Checkbox item for people not wanting MD5 anymore. - Storing passwords on the server in a securely hashed way, so the admin won’t know your password. - PostgreSQL developers getting out of the roll-your-own-crypto game.
28.
by petereisentraut 9y ago
The new logical replication feature is based on the experiences from BDR and pglogical, but it isn't multimaster yet.
29.
by petereisentraut 9y ago
fixed, thanks
30.
by petereisentraut 9y ago
Or if you use Homebrew you might like: brew install --devel petere/postgresql/postgresql@10

More ›