|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||Robert Haas <robertmhaas(at)gmail(dot)com>|
|Cc:||Jakob Egger <jakob(at)eggerapps(dot)at>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: PG_DIAG_SEVERITY and a possible bug in pq_parse_errornotice()|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> I don't have strong feelings about this. Technically, this issue
> affects 9.5 also, because pqmq.c was introduced in that release. I
> don't think we want to add another error field in a released branch.
> However, since there's no parallel query in 9.5, only people who are
> accessing that functionality via extension code would be affected,
> which might be nobody and certainly isn't a lot of people, so we could
> just leave this unfixed in 9.5.
After sleeping on it, I think the right answer is to introduce the new
error-message field (and not worry about 9.5). Will work on a patch
for that, unless I hear objections pretty soon.
regards, tom lane
|Next Message||Michael Paquier||2016-08-26 12:12:56||Re: Renaming of pg_xlog and pg_clog|
|Previous Message||Heikki Linnakangas||2016-08-26 11:53:11||Re: [Patch] RBTree iteration interface improvement|