Re: postgres_fdw vs data formatting GUCs (was Re: [v9.3] writable foreign tables)

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daniel Farina <daniel@heroku.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2013-03-20T14:43:57Z
Lists: pgsql-hackers
Daniel Farina <daniel@heroku.com> writes:
> Okay, one more of those fridge-logic bugs.  Sorry for the noise. v5.

> A missing PG_RETHROW to get the properly finally-esque semantics:

> --- a/contrib/dblink/dblink.c
> +++ b/contrib/dblink/dblink.c
> @@ -642,7 +642,10 @@ dblink_fetch(PG_FUNCTION_ARGS)
>   }
>   PG_CATCH();
>   {
> + /* Pop any set GUCs, if necessary */
>   restoreLocalGucs(&rgs);
> +
> + PG_RE_THROW();
>   }
>   PG_END_TRY();

Um ... you shouldn't need a PG_TRY for that at all.  guc.c will take
care of popping the values on transaction abort --- that's really rather
the whole point of having that mechanism.

			regards, tom lane


Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Fix postgres_fdw's issues with inconsistent interpretation of data values.