Peter Geoghegan wrote: > On Fri, Oct 24, 2014 at 4:39 PM, Petr Jelinek <p...@2ndquadrant.com> wrote:
> > Ugh, you want to auto-magically detect what value is behind the EXCLUDED > > based on how/where it's used in the UPDATE? That seems like quite a bad > > idea. > > That's *exactly* how DEFAULT works within UPDATE targetlists. There > might be a few more details to work out here, but not terribly many, > and that's going to be true no matter what. 95%+ of the time, it'll > just be "val = EXCLUDED" anyway. Petr's thought mirrors mine. What are you going to do the other 5% of the time? Is there some other way to refer to the columns of the "excluded" row? -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
