| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [COMMITTERS] pgsql: Add PGDLLIMPORT to ScanKeywords and NumScanKeywords. |
| Date: | 2012-03-31 17:17:12 |
| Message-ID: | 22075.1333214232@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 03/31/2012 11:59 AM, Tom Lane wrote:
>> The only simple fix I can see is to rename the symbols in ecpg and
>> pg_dump to something else. This is probably a good thing anyway to
>> reduce confusion. Anybody have another idea?
> Seems the sane thing to do.
Done, we'll see how the buildfarm likes this version ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-03-31 18:43:07 | pgsql: Fix O(N^2) behavior in pg_dump for large numbers of owned sequen |
| Previous Message | Tom Lane | 2012-03-31 17:16:04 | pgsql: Rename frontend keyword arrays to avoid conflict with backend. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-03-31 19:56:41 | Re: pg_dump incredibly slow dumping a single schema from a large db |
| Previous Message | Andrew Dunstan | 2012-03-31 16:52:37 | Re: [COMMITTERS] pgsql: Add PGDLLIMPORT to ScanKeywords and NumScanKeywords. |