On Thu, 2007-08-30 at 21:00 -0400, Tom Lane wrote:
> "Florian G. Pflug" <[EMAIL PROTECTED]> 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
On Sat, Sep 01, 2007 at 11:07:55PM -0400, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > On Sat, Sep 01, 2007 at 10:51:48PM -0400, Tom Lane wrote:
> >> Er ... what deficiency do you see in ALTER ROLE SET and ALTER DATABASE SET?
>
> > You can't set both at once.
>
> Oh, you mean th
David Fetter <[EMAIL PROTECTED]> writes:
> On Sat, Sep 01, 2007 at 10:51:48PM -0400, Tom Lane wrote:
>> Er ... what deficiency do you see in ALTER ROLE SET and ALTER DATABASE SET?
> You can't set both at once.
Oh, you mean the cross-product case. Sorry, that was on the wish-list
already, but no
On Sat, Sep 01, 2007 at 10:51:48PM -0400, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > While we're at it, it would be very nice to be able to set default
> > per-role, per-database settings.
>
> Er ... what deficiency do you see in ALTER ROLE SET and ALTER DATABASE SET?
You can'
David Fetter <[EMAIL PROTECTED]> writes:
> While we're at it, it would be very nice to be able to set default
> per-role, per-database settings.
Er ... what deficiency do you see in ALTER ROLE SET and ALTER DATABASE SET?
regards, tom lane
---(end o
On Thu, Aug 30, 2007 at 10:34:42PM +0100, Simon Riggs wrote:
> Async Commit is a useful feature, yet it requires some additional
> application code to be added to appropriate transactions. That code is
> then clearly version dependent, which may not always be desirable.
>
> It would be good if the
"Florian G. Pflug" <[EMAIL PROTECTED]> 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 a
Simon Riggs wrote:
Async Commit is a useful feature, yet it requires some additional
application code to be added to appropriate transactions. That code is
then clearly version dependent, which may not always be desirable.
It would be good if there was a way to make that a DBA-controllable
setti
"Simon Riggs" <[EMAIL PROTECTED]> writes:
> Perhaps it would be possible to do this
>
> ALTER FUNCTION fubar SET synchronous_commit = off;
>
> So that any invocation of the function would automatically set all of
> the appropriate parameters prior to execution.
The problem here is that fun
