Re: Make CREATE AGGREGATE check validity of initcond value? - Mailing list pgsql-hackers

From Jaime Casanova
Subject Re: Make CREATE AGGREGATE check validity of initcond value?
Date
Msg-id CAJKUy5gbLH=zeFpAxcrNNDq05LgfqU92A-cgd5fLY756pO6p3Q@mail.gmail.com
Whole thread Raw
In response to Make CREATE AGGREGATE check validity of initcond value?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
<p><br /> El 03/10/2012 21:38, "Tom Lane" <<a href="mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>> escribió:<br
/>><br /> > Does anyone have an objection to this?  I can imagine cases where the<br /> > check would reject
valuesthat would get accepted at runtime, if the<br /> > type's input function was sensitive to the phase of the
moonor<br /> > something.  But it doesn't seem very probable, whereas checking the<br /> > value seems like an
eminentlyuseful thing to do.  Or maybe I'm just<br /> > overreacting to the report --- I can't recall any previous
complaints<br/> > like this, so maybe entering a bogus initcond is a corner case too.<p>I guess a wrong initcond
value,probably is a pilot error. <br /> So, my first reaction is +1 to make it an error.<br /><br /> But if you feel
therea corner cases maybe at least a warning<p>--<br /> Jaime Casanova<br /> 2ndQuadrant: Your PostgreSQL partner <br
/>

pgsql-hackers by date:

Previous
From: "Greg Sabino Mullane"
Date:
Subject: Re: PQping command line tool
Next
From: Fujii Masao
Date:
Subject: Re: Promoting a standby during base backup (was Re: Switching timeline over streaming replication)