Re: patch for parallel pg_dump
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Robert Haas <robertmhaas@gmail.com>, Joachim Wieland <joe@mcknight.de>, Pg Hackers <pgsql-hackers@postgresql.org>, Andrew Dunstan <andrew@dunslane.net>
Date: 2012-04-03T16:10:55Z
Lists: pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes: > That only leaves assert_enabled to be handled. In the backend it lives > in guc.c; what to do about frontend code? There's no mechanism for turning such a switch on or off in most frontend code anyway. I'd think it could just be assumed to be on in the frontend implementation --- ie, frontend Asserts would always be active in --enable-cassert builds. There's not really any need to do better until/unless we start having Asserts that impact performance on the frontend side. regards, tom lane