| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Susan Cassidy <susan(dot)cassidy(at)decisionsciencescorp(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Steven Schlansker <steven(at)likeness(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: any way for a transaction to "see" inserts done earlier in the transaction? |
| Date: | 2014-04-17 00:33:43 |
| Message-ID: | 534F2167.6010604@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 04/16/2014 05:24 PM, Susan Cassidy wrote:
> I marked it volatile, and still the next time I call the function after
> the first insert, using the previous new id as as input parameter, it
> still can't "find" the newly inserted id for the next go-round. Nor can
> any regular SELECTs in the main program find it.
A suggestion would be to tail -f the postgres log file and see if there
is more than one connection happening when you run the program. This
assumes the database activity is quiet enough to distinguish connections.
>
> Susan
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert DiFalco | 2014-04-17 00:34:06 | Re: Re: any way for a transaction to "see" inserts done earlier in the transaction? |
| Previous Message | David G Johnston | 2014-04-17 00:28:22 | Re: any way for a transaction to "see" inserts done earlier in the transaction? |