Prev: named parameters in SQL functions
Next: [HACKERS] ORDER BY vs. volatile functions
From: Marko Tiikkaja on 30 Nov 2009 14:00
Tom Lane wrote:
> It would be
> altogether cleaner though if the CommandCounterIncrement responsibility
> were in the same place it is now, ie the caller of the executor. Which
> could be possible if we restructure the rewriter/planner output as a
> list of Queries instead of just one. I'm not currently sure how hard
> that would be, though; it might not be a practical answer.

I'm trying to avoid doing this, at least for now.


Regards,
Marko Tiikkaja

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Marko Tiikkaja on 7 Dec 2009 09:46
Tom Lane wrote:
> The only thing that I'd be comfortable with is
> copying the snap and modifying the copy.

I don't see an easy way to do that with the current code; CopySnapshot()
is static and PushUpdatedSnapshot() seems to be a bit of a pain since it
messes up some of the existing code which uses the active snapshot
stack. Any ideas?


Regards,
Marko Tiikkaja

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Alvaro Herrera on 7 Dec 2009 17:06
Marko Tiikkaja escribi�:
> Tom Lane wrote:
> >The only thing that I'd be comfortable with is
> >copying the snap and modifying the copy.
>
> I don't see an easy way to do that with the current code;
> CopySnapshot() is static and PushUpdatedSnapshot() seems to be a bit
> of a pain since it messes up some of the existing code which uses
> the active snapshot stack. Any ideas?

That API is rather new. Maybe we need a new entry point, say
GetActiveSnapshotCopy or some such.

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

First  |  Prev  | 
Pages: 1 2 3
Prev: named parameters in SQL functions
Next: [HACKERS] ORDER BY vs. volatile functions