Re: DOMAINs and CASTs - Mailing list pgsql-hackers

From Jaime Casanova
Subject Re: DOMAINs and CASTs
Date
Msg-id CAJKUy5jZ-3ccn_cC_g6Vy8-DVmYkeJn9K=w-pJGzWLLRSi8hBQ@mail.gmail.com
Whole thread Raw
In response to Re: DOMAINs and CASTs  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: DOMAINs and CASTs  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Tue, Nov 29, 2011 at 10:12 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Tue, Nov 29, 2011 at 11:11 AM, Jaime Casanova <jaime@2ndquadrant.com> wrote:
>> On Tue, Nov 29, 2011 at 10:42 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> Bruce Momjian <bruce@momjian.us> writes:
>>>> Tom Lane wrote:
>>>>> Robert Haas <robertmhaas@gmail.com> writes:
>>>>>> Well, if we apply this, it has the possibility to break existing
>>>>>> dumps.
>>>
>>> BTW, it occurs to me that we could dodge that objection, with much less
>>> work than Robert suggests, if we just made the message be a WARNING not
>>> an ERROR.  I think that'd do just as well in terms of what the message
>>> could usefully accomplish, ie, steer people away from doing things that
>>> won't work.  Still not sure that it's worth doing though,
>>>
>>
>> i'm fine with a WARNING
>
> Me too; I suggested it before (so did you).
>

are we going to put this warning in this release?

--
Jaime Casanova         www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: [BUG] Checkpointer on hot standby runs without looking checkpoint_segments
Next
From: Boszormenyi Zoltan
Date:
Subject: Re: [PATCH] lock_timeout and common SIGALRM framework