Hi,
Thank you for your kind answers and for not having killed me despite
the fact that I report a bu^H^H documented feature. It had no impact
on me since there's an easy workaround to this behaviour (like you
reported), I just really thought it was a bug...
Sorry guys,
Thibauld
2008/7/8 Tom Lane
"Heikki Linnakangas" <[EMAIL PROTECTED]> writes:
> Thibauld Favre wrote:
>> Here's what I get as a result on my server. See how 'a' is systematically
>> put at the end of the result set until the LIMIT clause reaches the value 8.
>> Above 8, the results get consistent again.
> Doesn't look like a
Thibauld Favre escribió:
> Here's a little SQL script that recreate the bug I encounter on my app.
> Basically, on certain circonstances, the first value of the table (here 'a')
> is constantly returned at the end of the result set, thus creating
> inconsistency between queries. I'm not sure I'm c
Thibauld Favre wrote:
Here's a little SQL script that recreate the bug I encounter on my app.
Basically, on certain circonstances, the first value of the table (here 'a')
is constantly returned at the end of the result set, thus creating
inconsistency between queries. I'm not sure I'm clear so he
The following bug has been logged online:
Bug reference: 4286
Logged by: Thibauld Favre
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.3
Operating system: Ubuntu Hardy Heron (8.04.1)
Description:ORDER BY returns inconsistent results when using LIMIT
on a int
