| From: | Richard Broersma Jr <rabroersma(at)yahoo(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | General PostgreSQL List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: visibility rules for AFTER UPDATE Constraint Triggers Function |
| Date: | 2008-01-02 13:44:56 |
| Message-ID: | 914600.47286.qm@web31807.mail.mud.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
--- On Tue, 1/1/08, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Please provide a self-contained example.
Basically the example demonstrates the difference a single tuple UPDATE when preformed the following two ways:
UPDATE table ...; -- Sees OLD.
BEGIN; UPDATE table ...; COMMIT; --Sees NEW.
I was my understanding that all single DML statement are wrapped in their own transaction so I thought that these two statements should preform the same.
Regards,
Richard Broersma Jr.
| Attachment | Content-Type | Size |
|---|---|---|
| =?utf-8?q?sampledb.dump.txt?= | text/plain | 14.6 KB |
| =?utf-8?q?testcase.txt?= | text/plain | 2.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Glyn Astill | 2008-01-02 13:47:19 | Fwd: [ADMIN] Shutting down warm standby server? " |
| Previous Message | Pavel Stehule | 2008-01-02 13:19:51 | Re: group by and count(*) behaviour in 8.3 |