> -Original Message-
> From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-
> It'd be really interesting to relax that limitation to "... other
> non-read-only transaction ... " and have a database that's being cloned
> block or reject
> DML, UPDATE, etc. There are some issues wi
> -Original Message-
> From: Jeff Davis [mailto:pg...@j-davis.com]
>
> On Mon, 2012-06-18 at 21:35 +, Haszlakiewicz, Eric wrote:
> > I'm trying to get some additional information back from a trigger to
> > my embedded SQL program, to essentially emulate I
I'm trying to get some additional information back from a trigger to my
embedded SQL
program, to essentially emulate Informix's way of generating serial values.
I can get the serial to be generated, but I'm trying to figure out how to get
the
generated value back to my program with minimal change
>-Original Message-
>From: pgsql-performance-ow...@postgresql.org
>
>We use a typical counter within a transaction to generate
>order sequence number and update the next sequence number.
>This is a simple next counter - nothing fancy about it. When
>multiple clients are concurrently a
