Re: [HACKERS] Re: pgsql: Extract catalog info for error reporting before an error actually - Mailing list pgsql-committers

From Andrew Dunstan
Subject Re: [HACKERS] Re: pgsql: Extract catalog info for error reporting before an error actually
Date
Msg-id 4720D794.1090509@dunslane.net
Whole thread Raw
In response to pgsql: Extract catalog info for error reporting before an error actually  (alvherre@postgresql.org (Alvaro Herrera))
Responses Re: [HACKERS] Re: pgsql: Extract catalog info for error reporting before an error actually  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-committers

Michael Paesold wrote:
> In the previous discussion, Simon and me agreed that schema changes
> should not happen on a regular basis on production systems.
>
> Shouldn't we rather support the regular usage pattern instead of the
> uncommon one? Users doing a lot of schema changes are the ones who
> should have to work around issues, not those using a DBMS sanely. No?
>
>

Unfortunately, doing lots of schema changes is a very common phenomenon.
It makes me uncomfortable too, but saying that those who do it have to
work around issues isn't acceptable IMNSHO - it's far too widely done.

cheers

andrew

pgsql-committers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] Re: pgsql: Extract catalog info for error reporting before an error actually
Next
From: Michael Paesold
Date:
Subject: Re: [HACKERS] Re: pgsql: Extract catalog info for error reporting before an error actually