From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
---|---|
To: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
Subject: | Re: tuplesort Generation memory contexts don't play nicely with index builds |
Date: | 2022-07-07 02:13:54 |
Message-ID: | CAApHDvr3P6WRZzB236usUTDs060SOm=D-hkN+EK5m6WMPHcNtA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 7 Jul 2022 at 13:41, John Naylor <john(dot)naylor(at)enterprisedb(dot)com> wrote:
>
> On Thu, Jul 7, 2022 at 3:16 AM David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> >
> > Pushed.
>
> Hmm, the commit appeared on git.postgresql.org, but apparently not in
> my email nor the list archives.
Strange. I'd suspect a temporary hiccup in whatever code pushes the
commits onto the mailing list, but I see that my fe3caa143 from
yesterday was also missed.
The only difference in my workflow is that I'm sshing to the machine I
push from via another room rather than sitting right in front of it
like I normally am. I struggle to imagine why that would cause this to
happen.
David
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2022-07-07 02:50:36 | Re: [BUG] Logical replication failure "ERROR: could not map filenode "base/13237/442428" to relation OID" with catalog modifying txns |
Previous Message | David Rowley | 2022-07-07 01:54:46 | Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower |