From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | Re: pgsql: Don't Memoize lateral joins with volatile join conditions |
Date: | 2023-08-07 23:52:08 |
Message-ID: | CAApHDvon5fJ6uXBTr2zB0vDUhuzWwknXOohARpzghuy5zMgjyw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
On Tue, 8 Aug 2023 at 10:06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> > * https://wiki.postgresql.org/wiki/Committing_checklist
>
> I thought we had something written down there after the last
> discussion of this point, but maybe it was hanging fire because
> we hadn't chosen a specific definition of when to start the pause.
Probably something wider to provide some margin is likely better than
it not being documented at all.
> I'm just whining because this wasn't following process.
I understand. I certainly don't want to be the cause of the
destabilisation of a release.
It's just frustrating when trying to follow the process but the lack
of documentation about what that process is just leaves it to
trial/error/someone complaining.
David
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2023-08-08 17:41:10 | Re: pgsql: Some refactoring to export json(b) conversion functions |
Previous Message | Michael Paquier | 2023-08-07 23:24:12 | pgsql: doc: Fix incorrect entries generated from wait_event_names.txt |