| From: | Susan Cassidy <susan(dot)cassidy(at)decisionsciencescorp(dot)com> |
|---|---|
| To: | 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:18:40 |
| Message-ID: | CAE3Q8o=m5yn+idoRgraXOnKuVz+EFNDbbjBf0vh-mcsEPCcWSg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
It isn't marked as one of those as all, so whatever the default is.
That could be it. I'll look up the default.
Thanks,
Susan
On Wed, Apr 16, 2014 at 5:17 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Susan Cassidy <susan(dot)cassidy(at)decisionsciencescorp(dot)com> writes:
> > It is a fairly large and complex Perl program, so no, not really.
> > I do an insert via a function, which returns the new id, then later I try
> > to SELECT on that id, and it doesn't find it.
>
> > Could it be because the insert is done inside a function?
>
> Is the SELECT also inside a database function, and if so is that function
> marked stable or immutable? That might explain it --- non-volatile
> functions are intentionally designed not to notice updates that happen
> after they start.
>
> regards, tom lane
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Susan Cassidy | 2014-04-17 00:24:55 | Re: any way for a transaction to "see" inserts done earlier in the transaction? |
| Previous Message | Tom Lane | 2014-04-17 00:17:01 | Re: any way for a transaction to "see" inserts done earlier in the transaction? |