On 3/6/17 12:48 PM, Robert Haas wrote:
Mark pg_start_backup and pg_stop_backup as parallel-restricted.
They depend on backend-private state that will not be synchronized by
the parallel machinery, so they should not be marked parallel-safe.
This issue also exists in 9.6, but we obviously can't
On 4/16/16 4:44 PM, Noah Misch wrote:
> The key judgment to finalize here is whether it's okay to release this feature
> given its current effect[1], when enabled, on performance. That is more
> controversial than the potential ~2% regression for old_snapshot_threshold=-1.
> Alvaro[2] and
On 9/22/15 11:00 AM, Andrew Dunstan wrote:
On 09/22/2015 10:29 AM, Geoff Winkless wrote:
That's your opinion; my opinion remains otherwise. It's not
"perfectly reasonable" to abuse the plural because some 1960s
feminazis either misunderstood or didn't like the fact that (because
of history)
;/* should this be DDL? */
break;
and the fact that CLUSTER is DDL. I'm not married to REINDEX as DDL,
though. I'm happy to make it consistent with core. If it changes in
core, it would also change in pg_audit.
--
- David Steele
da...@pgmasters.net
signature.asc
Description
