daveg <[EMAIL PROTECTED]> writes:
> Are we talking about the same patch?
Maybe not --- I thought you were talking about a backend-side behavioral
> Because I don't know what you are
> refering to with "timer management code" and "scheduling the interrupt" in
> the context of pg_dump.
I'm not sure that I see a good argument for making pg_dump deliberately
fail, if that's what you're proposing. Maybe I'm just too old-school,
but there simply is not any other higher priority for a database than
safeguarding your data.
regards, tom lane
Sent via pgsql-patches mailing list (email@example.com)
To make changes to your subscription: