"Greg Sabino Mullane" <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Please try the attached patch (in addition to the one I sent earlier).
> This is biting us too, quite badly. Any chance this can get pushed into a
> 8.2.6?
Those patches are certainly already in the 8.2 CVS branch, so your
qu
"Rene Gollent" <[EMAIL PROTECTED]> writes:
> If you issue a REINDEX DATABASE, which then fails due to db corruption (i.e.
> could not create index due to duplicate values), the resulting error message
> only specifies:
> ERROR: could not create unique index
> DETAIL: Table contains duplicated val
The following bug has been logged online:
Bug reference: 3707
Logged by: Rene Gollent
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: Linux (Gentoo)
Description:failure cases in reindex don't always report enough
information to diagnose th
Jakub Ouhrabka <[EMAIL PROTECTED]> writes:
>> By "last patch" you mean
>> http://archives.postgresql.org/pgsql-committers/2007-10/msg00409.php
> Sorry for confusion, I meant this one:
> http://archives.postgresql.org/pgsql-bugs/2007-10/msg00217.php
> Is it the same as the commited one?
Yeah, shou
By "last patch" you mean
http://archives.postgresql.org/pgsql-committers/2007-10/msg00409.php
?
Sorry for confusion, I meant this one:
http://archives.postgresql.org/pgsql-bugs/2007-10/msg00217.php
Is it the same as the commited one?
If so that's about as fast as it's likely to get. 22
Jakub Ouhrabka <[EMAIL PROTECTED]> writes:
> I've also tried your last patch but still for some queries there is long
> planning time, e.g. more than 30s on a fast machine for query with 14
> regularly JOINed tables plus 8 tables are LEFT OUTER JOINed (all normal
> joins are followed by all oute
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Tom Lane wrote:
> Please try the attached patch (in addition to the one I sent earlier).
This is biting us too, quite badly. Any chance this can get pushed into a
8.2.6?
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 20071029
The following bug has been logged online:
Bug reference: 3706
Logged by: Scott Bailey
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3beta1
Operating system: Tru64
Description:ecpg regression: "MOVE FORWARD"
Details:
The following statement:
exec sql MOVE F
Hi Tom,
...probably have some cases like that in your real application. But I'd
expect 8.2.4 to be equally slow because it also contains the code that
is slow in that scenario. I'm hoping to get some time today to think
about how that could be fixed.
Please try the attached patch (in additio
