| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
| Cc: | PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Stability of queryid in minor versions |
| Date: | 2024-04-15 01:36:19 |
| Message-ID: | CAKFQuwaLVg7Nz7is5zxi+SXbZNYH25xg1ErjWkuM96x5DOqooA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Apr 14, 2024 at 4:20 PM David Rowley <dgrowleyml(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2024-04-15 01:46:00 | Re: ALTER TABLE SET ACCESS METHOD on partitioned tables |
| Previous Message | David Rowley | 2024-04-15 01:31:47 | Re: Stability of queryid in minor versions |