| From: | "Vadim Mikheev" <vmikheev(at)sectorbase(dot)com> |
|---|---|
| To: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Alex Pilosov" <alex(at)pilosoft(dot)com>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: time stops within transaction |
| Date: | 2000-10-19 18:55:18 |
| Message-ID: | 00fd01c039fe$20752b40$bb7a30d0@sectorbase.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I am inclined to think that we should do SetQuerySnapshot in the outer
> loop of pg_exec_query_string, just before calling
> pg_analyze_and_rewrite. This would ensure that parse/plan accesses to
^^^^^^^^^^^^^^
Actually not - snapshot is passed as parameter to heap_beginscan...
And currently SnapshotNow is used everywhere.
> If we did that, then SetQuerySnapshot would be called once per user-
> written command (defining a command as whatever the grammar produces
> a single parsetree for, which is probably OK) so long as SPI functions
> don't try to use pg_exec_query_string...
SPI doesn't try this from its birthday in ~6.2
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2000-10-19 18:55:55 | Re: [ANNC][RFC] crypto hashes for PostgreSQL 7.0, 7.1 |
| Previous Message | Tom Lane | 2000-10-19 18:46:38 | Re: SetQuerySnapshot() for utility statements |