Whats the reason for disallowing cursors on wCTEs? I am not sure I can follow
* We also disallow data-modifying WITH in a cursor. (This could be
* allowed, but the semantics of when the updates occur might be
errmsg("DECLARE CURSOR must not contain data-modifying
statements in WITH")));
Given that cursors are about the only sensible way to return larger amounts of
data, that behaviour reduces the usefulness of wCTEs a bit.
Whats the exact cause of concern here? I personally don't think there is a
problem documenting that you should fetch the cursor fully before relying on
the updated tables to be in a sensible state. But that may be just me.
pgsql-hackers by date
|Next:||From: Euler Taveira de Oliveira||Date: 2011-09-21 16:22:22|
|Subject: Re: Hot Backup with rsync fails at pg_clog if under load|
|Previous:||From: Heikki Linnakangas||Date: 2011-09-21 16:13:20|
|Subject: Re: Inlining comparators as a performance optimisation|