Skip site navigation (1) Skip section navigation (2)

Re: [COMMITTERS] pgsql: Add PGDLLIMPORT to ScanKeywords and NumScanKeywords.

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 (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-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

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2012-03-31 19:56:41
Subject: Re: pg_dump incredibly slow dumping a single schema from a large db
Previous:From: Andrew DunstanDate: 2012-03-31 16:52:37
Subject: Re: [COMMITTERS] pgsql: Add PGDLLIMPORT to ScanKeywords and NumScanKeywords.

pgsql-committers by date

Next:From: Tom LaneDate: 2012-03-31 18:43:07
Subject: pgsql: Fix O(N^2) behavior in pg_dump for large numbers of ownedsequen
Previous:From: Tom LaneDate: 2012-03-31 17:16:04
Subject: pgsql: Rename frontend keyword arrays to avoid conflict with backend.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group