| From: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
|---|---|
| To: | Erik Rijkers <er(at)xs4all(dot)nl> |
| Cc: | Marco Nenciarini <marco(dot)nenciarini(at)devise(dot)it>, Noah Misch <noah(at)leadboat(dot)com>, Gabriele Bartolini <gabriele(dot)bartolini(at)2ndquadrant(dot)it>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Support for foreign keys with arrays |
| Date: | 2012-02-21 18:45:15 |
| Message-ID: | CAEYLb_WhXy74NBkh0AF7dwrh=3W6HD_r1ZcZ1aj8xDpjZ-568Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 21 February 2012 15:22, Erik Rijkers <er(at)xs4all(dot)nl> wrote:
> (I reply to an older message but I did use the newest patch, version 3)
>
> I wanted to have a look at v3 of this patch today, but it seems it won't apply and compile anymore.
That's just because a new column has been added to pg_proc -
proleakproof. Generalise from the example of commit
cd30728fb2ed7c367d545fc14ab850b5fa2a4850 - it modified ever pg_proc
entry, and this patch needs the same treatment:
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2012-02-21 18:54:03 | Re: REASSIGN OWNED lacks support for FDWs |
| Previous Message | Tom Lane | 2012-02-21 18:21:31 | Re: Unfamous 'could not read block ... in file "...": read only 0 of 8192 bytes' again |