Skip site navigation (1) Skip section navigation (2)

Re: synchronous_commit: Developer's View

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: synchronous_commit: Developer's View
Date: 2007-08-31 01:00:39
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
"Florian G. Pflug" <fgp(at)phlo(dot)org> writes:
> ... So at least for the pl/pgsql case, it seems easy enough to temporarily
> change GUCs already. For other PLs, things might be different though -
> I wouldn't know, I have never really used them...

It's definitely possible, but it's inconvenient and slow (slow because
you have to run a subtransaction, which ain't cheap).  I think Simon
might have a good point about generalizing the proposed "set the search
path" facility to instead be "set any GUC for the duration of this
function".  He's definitely all wet about the usefulness of that for
synchronous_commit, but as Greg pointed out, there are other GUCs
besides search_path that can break a function's expectations.

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2007-08-31 01:05:36
Subject: Re: Advice on MyXactMade* flags, MyLastRecPtr, pendingDeletes and lazy XID assignment
Previous:From: Florian G. PflugDate: 2007-08-31 00:35:01
Subject: Re: synchronous_commit: Developer's View

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group