> 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
- Re: [HACKERS] time stops within tra... Peter Eisentraut
- Re: [HACKERS] time stops within tra... Don Baccus
- Re: [HACKERS] time stops within tra... Alex Pilosov
- Re: [HACKERS] time stops within... Tom Lane
- Re: [HACKERS] time stops within... Hiroshi Inoue
- Re: [HACKERS] time stops within... Tom Lane
- Re: [HACKERS] time stops within... Hiroshi Inoue
- Re: [HACKERS] time stops within... Vadim Mikheev
- Re: [HACKERS] time stops within... Hiroshi Inoue
- Re: [HACKERS] time stops within... Tom Lane
- Re: [HACKERS] time stops within... Vadim Mikheev
- Re: [HACKERS] time stops within... Hiroshi Inoue
- RE: [HACKERS] time stops within... Hiroshi Inoue
- Re: [HACKERS] time stops within transaction Karel Zak
- Re: [HACKERS] time stops within transaction Mikheev, Vadim