From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Emit extra debug message when executing extension script. |
Date: | 2022-07-01 22:24:27 |
Message-ID: | b4a190ddb4419131281c61c66e511544632c37c2.camel@j-davis.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 2022-06-29 at 21:39 -0400, Robert Haas wrote:
> > This should either be elog or use errmsg_internal.
>
> Why?
I didn't see a response, so I'm still using ereport(). I attached a new
version though that doesn't emit the actual script filename; instead
just the from/to version.
The output looks nicer and I don't have to worry about whether the user
should be able to know the share directory or not.
Regards,
Jeff Davis
Attachment | Content-Type | Size |
---|---|---|
v2-0001-Emit-debug-message-when-executing-extension-script.patch | text/x-patch | 1.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Nathan Bossart | 2022-07-01 22:33:33 | Re: Emit extra debug message when executing extension script. |
Previous Message | Nathan Bossart | 2022-07-01 22:23:26 | Re: Time to remove unparenthesized syntax for VACUUM? |