Re: Identifying no-op length coercions - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Identifying no-op length coercions
Date
Msg-id BANLkTikQBH2HJ-9EnqqDEMbFOyM3Ly9dFw@mail.gmail.com
Whole thread Raw
In response to Re: Identifying no-op length coercions  (Noah Misch <noah@leadboat.com>)
Responses Re: Identifying no-op length coercions
List pgsql-hackers
On Sat, Jun 11, 2011 at 5:13 PM, Noah Misch <noah@leadboat.com> wrote:
> Sounds good.  Updated patch attached, incorporating your ideas.  Before applying
> it, run this command to update the uninvolved pg_proc.h DATA entries:
>  perl -pi -e 's/PGUID(\s+\d+){4}/$& 0/' src/include/catalog/pg_proc.h

This doesn't quite apply any more.  I think the pgindent run broke it slightly.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [v9.2] DROP Reworks Part.0 - 'missing_ok' support of get_object_address
Next
From: Robert Haas
Date:
Subject: Re: crash-safe visibility map, take five