Hello.
In spite of the fact that as it was outlined in the "change log" to PostgreSQL
8.2.2, the bug of the periodical "permission denied" error occurrence was fixed:
"Fix bogus "permission denied" failures occurring on Windows due to attempts
to fsync already-deleted files (Magnus, Tom
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> This also ties into the discussions we've had off-and-on about making
> catalog lookups behave in an MVCC fashion instead of using SnapshotNow.
> I'm still pretty hesitant to go there, but maybe we could do something
> involving MVCC for unloc
"Steve Gieseking" <[EMAIL PROTECTED]> writes:
> I am maintaining code that uses ecpg. The following query was working with
> the previous version of ecpg:
> ...
> The problem is the translation to ensable. This appears to be caused by the
> file 'preproc.y' at the line:
> | ENABLE_P
The following bug has been logged online:
Bug reference: 3183
Logged by: Murali
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: Windows
Description:set maximum row to retrieve + postgresql.conf
Details:
Dear All,
Right now it's allowing
The following bug has been logged online:
Bug reference: 3181
Logged by: Steve Gieseking
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.3
Operating system: Linux Fedora Core 6
Description:ecpg generating wrong code
Details:
I am maintaining code that uses
TANIDA Yutaka <[EMAIL PROTECTED]> writes:
> Hi,
>
> On Thu, 22 Mar 2007 07:48:18 +
> Heikki Linnakangas <[EMAIL PROTECTED]> wrote:
>
>> Can you reproduce this with 8.2?
>
> Yes, I can.
This ...
>
> [EMAIL PROTECTED] tmp]$ psql -p 54382
> Welcome to psql 8.1.2 (server 8.2.3), the PostgreSQL
The following bug has been logged online:
Bug reference: 3182
Logged by: CN Liou
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.3
Operating system: Win98
Description:Cannot make libpq with BCC 5.5
Details:
bcc32.exe
-I\borland\bcc55\include;..\..\include;.
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom, do you want this fixed for 8.2.X?
> Tom Lane wrote:
>> Yeah. I'd say that intarray's attempt to override the default status of
>> the built-in gin opclass is simply a bad idea and should be removed.
I don't recall having seen a response from Oleg
Tom, do you want this fixed for 8.2.X?
---
Tom Lane wrote:
> "Dmitry Koterov" <[EMAIL PROTECTED]> writes:
> > [ pg_restore fails with ]
> > ERROR: could not make operator class "gin__int_ops" be default for type
> > pg_cata
