Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Daniel Gustafsson <dgustafsson(at)pivotal(dot)io>, ANASTACIO Tiago <tiago_anastacio(at)yahoo(dot)fr>, Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker
Date: 2019-10-17 01:07:51
Message-ID: CA+hUKGLJyhG1A5=+xRFAnezV-HM=RX+L2qS-An2p34_+Xr_niw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sat, Apr 13, 2019 at 4:47 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Michael Paquier <michael(at)paquier(dot)xyz> writes:
> > On Thu, Apr 11, 2019 at 11:04:14AM -0400, Tom Lane wrote:
> >> The extra appearance of "parallel worker" seems a bit redundant,
> >> though I don't know if we can get rid of it.
> >>
> >> Could we at least be consistent about whether the context is
> >> "parallel worker" or "parallel worker process"?
>
> > Indeed. My vote would be to back-patch that stuff.

Done. Apologies for the delay.

> After thinking about it some more: can't we just make the new context
> message be
> CONTEXT: while setting parameter "x" to "y"
> full stop? The outer context line about "parallel worker" should
> be enough for that. As a bonus, if we ever decide that such a
> context line would be useful for all GUC errors, we wouldn't need
> a different spelling of it for that.

Agreed. I changed that before pushing.

> I took a quick look through the patch, and I think it's okay
> implementation-wise, though personally I'd have used some less
> generic name than "pair" for the variables.

I changed it to error_context_name_and_value.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Thomas Munro 2019-10-17 01:31:02 Re: BUG #16026: default_tablespace in postgresql.conf is used instead of the database's default.
Previous Message Thomas Munro 2019-10-16 23:25:08 Re: ERROR: multixact X from before cutoff Y found to be still running