Re: Add LINE: hint when schemaname.typename is a non-existent schema

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Ryan Kelly <rpkelly22(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Add LINE: hint when schemaname.typename is a non-existent schema
Date: 2015-03-17 19:46:14
Message-ID: 14399.1426621574@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> Agreed; the attached patch does it that way. (I notice that we have the
> pstate as first arg in many places; I put at the end for
> make_oper_cache_key, together with location. Is there some convention
> to have it as first arg?)

Yes, parser-related functions always have pstate as first arg if they
need it at all. Please follow that convention.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2015-03-17 20:01:20 Re: ranlib bleating about dirmod.o being empty
Previous Message Peter Geoghegan 2015-03-17 19:22:33 Re: INSERT ... ON CONFLICT IGNORE (and UPDATE) 3.0