| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | Amit Langote <amitlangote09(at)gmail(dot)com>, exclusion(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Subject: | Re: BUG #15668: Server crash in transformPartitionRangeBounds |
| Date: | 2019-03-11 07:21:14 |
| Message-ID: | 20190311072114.GG1818@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Mon, Mar 11, 2019 at 03:44:39PM +0900, Amit Langote wrote:
> We could make the error message more meaningful depending on the context,
> but maybe it'd better be pursue it as a separate project.
Yeah, I noticed that stuff when working on it this afternoon. The
error message does not completely feel right even in your produced
tests. Out of curiosity I have been working on this thing myself,
and it is possible to have a context-related message. Please see
attached, that's in my opinion less confusing, and of course
debatable. Still this approach does not feel completely right either
as that means hijacking the code path which generates a generic
message for missing RTEs. :(
--
Michael
| Attachment | Content-Type | Size |
|---|---|---|
| partbound-error.patch | text/x-diff | 6.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2019-03-11 08:49:47 | BUG #15685: pg_upgrade fails to migrate DEFAULT values that use custom TYPEs or FUNCTIONs |
| Previous Message | lichuancheng@highgo.com | 2019-03-11 06:52:50 | Re: Re: BUG #15567: Wal receiver process restart failed when a damaged wal record arrived at standby. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2019-03-11 07:23:39 | Fix volatile vs. pointer confusion |
| Previous Message | Amit Langote | 2019-03-11 06:44:39 | Re: BUG #15668: Server crash in transformPartitionRangeBounds |