Tomasz Ostrowski writes:
>> Also, the syntax looks wrong --- shouldn't the new calls be
>> AC_SEARCH_LIBS?
> Of course - my bad. I had to recreate a patch because I needed to return
> back this autoconf version check and haven't retested it. I'm attaching
> corrected and this time tested versio
On 2012-02-23 20:28, Tom Lane wrote:
Hmmm ... I'd be happier with this patch if it reversed the order of the
library probes (ie, try the nonstandard names first), as then it would
obviously not break any configurations that worked before. Would that
be OK from your point of view, or not?
It w
Tomasz Ostrowski writes:
> On 2012-02-23 19:51, tomet...@batory.org.pl wrote:
>> I've attached a proposed patch for configure.in
> The bug reporting form has word-wrapped my patch - I'm attaching a
> correct version.
Hmmm ... I'd be happier with this patch if it reversed the order of the
librar
On 2012-02-23 19:51, tomet...@batory.org.pl wrote:
I've attached a proposed patch for configure.in
The bug reporting form has word-wrapped my patch - I'm attaching a
correct version.
4. Run using "System Tools\Terminal":
su -c 'yum -y install mingw32-gcc mingw32-openssl gcc'
Sorr
The following bug has been logged on the website:
Bug reference: 6486
Logged by: Tomasz Ostrowski
Email address: tomet...@batory.org.pl
PostgreSQL version: 9.1.2
Operating system: Fedora Linux 16
Description:
Fedora MinGW is a project which allows for easy cross-compi
Ramanujam writes:
> On Thu, Feb 23, 2012 at 3:22 PM, Tom Lane wrote:
>> This is intentional --- we gave up updating index column names awhile
>> ago.
> Is pg_constraint a credible place to retrieve primary key information from?
I'd try the information_schema views first.
Marti Raudsepp writes:
> AFAICT, the model in the documentation suggests that the SELECT fields
> are evaluated for all matching rows in indeterminate order, before
> ORDER BY is applied and before the result set is sliced by
> OFFSET/LIMIT.
That is in fact the case if you have a query plan that
On 02/23/2012 12:05 AM, Marti Raudsepp wrote:
> On Wed, Feb 22, 2012 at 23:40, Tom Lane wrote:
>> Marti Raudsepp writes:
>>> According to this model, evaluating SELECT clause fields for *all*
>>> found rows is done in step 5, whereas LIMIT/OFFSET are only applied
>>> later at step 9. So we're alr
