The following bug has been logged online:
Bug reference: 5450
Logged by: gouthamj
Email address: jgowt...@gmail.com
PostgreSQL version: 8.1.5
Operating system: Window xp(sp2)
Description:system lacked sufficient buffer space, or because a
queue was full, could not per
"gouthamj" wrote:
> PostgreSQL version: 8.1.5
> Operating system: Window xp(sp2)
Sorry, PostgreSQL 8.1 on Windows is no longer supported.
Please upgrade to 8.2 or newer versions, and test your sequence again.
BTW, your message comes from WSAENOBUFS (10055). The error could be
raised by vario
The following bug has been logged online:
Bug reference: 5451
Logged by: Pavel Golub
Email address: pa...@microolap.com
PostgreSQL version: 8.4.x
Operating system: Windows
Description:pg_restore doesn't close input .tar archive
Details:
pg_restore doesn't close inpu
As discussed in irc://freenode/postgresql (2010-05-06 16:20)
Function bodies are checked using the _current_ search_path instead of
the search_path supplied by the "SET search_path" clause.
This leads to wrong error messages during creation.
On the other hand it can make a function body pass the ch
"Pavel Golub" writes:
> pg_restore doesn't close input .tar archive file after restore process.
> However, file is closed after pg_restore termination, I suppose it's not
> correct behaviour.
I'm not sure what distinction you're trying to draw. Do you want us to
add a close() just before exit()
The following bug has been logged online:
Bug reference: 5452
Logged by: Chris Copeland
Email address: ch...@cope360.com
PostgreSQL version: 8.2.16
Operating system: Solaris 10 x86
Description:Server core dumps coming out of recovery mode
Details:
I originally had t
Hello, Tom.
You wrote:
TL> "Pavel Golub" writes:
>> pg_restore doesn't close input .tar archive file after restore process.
>> However, file is closed after pg_restore termination, I suppose it's not
>> correct behaviour.
TL> I'm not sure what distinction you're trying to draw. Do you want us
