Re: [PATCH] PL/Python: Add spidata to all spiexceptions

From: Jan Urbański <wulczer(at)wulczer(dot)org>
To: "Karl O(dot) Pinc" <kop(at)meme(dot)com>
Cc: Oskari Saarenmaa <os(at)ohmu(dot)fi>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] PL/Python: Add spidata to all spiexceptions
Date: 2012-12-12 17:36:54
Message-ID: 50C8C0B6.8050606@wulczer.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Though not the original patch autor, I did modify and submit it to the
CF app, so I'll reply here :)

On 10/12/12 19:20, Karl O. Pinc wrote:
> On 12/09/2012 10:33:59 PM, Karl O. Pinc wrote:

> I've gone ahead and signed up to review this patch.

Thanks!

> There were 2 outstanding issue raised:
>
> Is this useful enough/proceeding in the right direction to commit
> now?

I believe the process would be to mark it as "Ready for Committer" if
you feel like it's ready and a then a committer would make the final call.

> Should some of the logic be moved out of a subroutine and into the
> calling code?

I think I structured the PLy_get_spi_sqlerrcode to accept the same kind
of arguments as PLy_get_spi_error_data, which means a SPIException
object and a pointer to whatever values it can fill in.

That said, I haven't really thought about that too much, so I'm
perfectly fine with moving that bit of logic to the caller.

Cheers,
Jan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2012-12-12 18:12:27 PRIVATE columns
Previous Message Pavan Deolasee 2012-12-12 17:31:14 Re: PageIsAllVisible()'s trustworthiness in Hot Standby