Re: Stability of queryid in minor versions
David G. Johnston <david.g.johnston@gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: David Rowley <dgrowleyml@gmail.com>
Cc: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2024-04-15T01:36:19Z
Lists: pgsql-hackers
On Sun, Apr 14, 2024 at 4:20 PM David Rowley <dgrowleyml@gmail.com> wrote: > > I've drafted a patch which I think improves things, but it probably > needs more work and opinions. > > Seems we can improve things by simply removing the "rule of thumb" sentence altogether. The prior paragraph states the things the queryid depends upon at the level of detail the reader needs. The sentence "Two servers participating in replication based on physical WAL replay can be expected to have identical queryid values for the same query." apparently assumes that to participate both servers must share the same machine architecture. I am under the impression that this is only an advisory, not a requirement. Rather, two servers participating in physical replication will be ensured that the catalog metadata and major versions are identical. This is not the case for servers related via logical replication. David J.
Commits
-
Doc: document cases where queryid is stable
- 74a587a009d1 12.19 landed
- e4c76f5eca92 13.15 landed
- c6e229d5f76f 14.12 landed
- 38daca854adb 15.7 landed
- 0d8931c12aa9 16.3 landed
- 2d3389c28c5c 17.0 landed