Re: Remembering bug #6123 - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: Remembering bug #6123
Date
Msg-id 4F0F0AF70200002500044750@gw.wicourts.gov
Whole thread Raw
In response to Re: Remembering bug #6123  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Remembering bug #6123  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.us> wrote:

> You forgot to attach the patch, but the approach seems totally
> Rube Goldberg to me anyway.  Why not just fix heap_update/
> heap_delete to return the additional information?  It's not like
> we don't whack their parameter lists around regularly.
>
> Rather than having three output parameters to support the case,
> I'm a bit inclined to merge them into a single-purpose struct
> type.  But that's mostly cosmetic.

OK, I got rid of the parrots and candles and added a structure to
hold the data returned only on failure.

Am I getting closer?

-Kevin


Attachment

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: ERRCODE_READ_ONLY_SQL_TRANSACTION
Next
From: Tom Lane
Date:
Subject: Re: ERRCODE_READ_ONLY_SQL_TRANSACTION