On Thu, Nov 25, 2010 at 05:28, Darryl Pye wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5767
> Logged by: Darryl Pye
> Email address: darryl...@hotmail.com
> PostgreSQL version: 9.01
> Operating system: Windows Server 2008
> Description: Memor
The following bug has been logged online:
Bug reference: 5770
Logged by: Martin Edlman
Email address: edl...@fortech.cz
PostgreSQL version: 9.0.1
Operating system: Scientific Linux 5.5 (RHEL)
Description:Foreign key violation after insert
Details:
Hello,
I have two
The following bug has been logged online:
Bug reference: 5768
Logged by: Pavel Arnost
Email address: pavel.arn...@loutka.cz
PostgreSQL version: 9.01
Operating system: N/A
Description:Inefficiency of large offsets should be mentioned on
SELECT documentation page
Detail
The following bug has been logged online:
Bug reference: 5769
Logged by: Helmar Spangenberg
Email address: hspangenb...@frey.de
PostgreSQL version: 9.0.1
Operating system: Linux
Description:Problem with SPI_getvalue
Details:
Referring to the manual, I can pfree the
On 25.11.2010 13:45, Helmar Spangenberg wrote:
Bug reference: 5769
Logged by: Helmar Spangenberg
Email address: hspangenb...@frey.de
PostgreSQL version: 9.0.1
Operating system: Linux
Description:Problem with SPI_getvalue
Details:
Referring to the manual, I can pfree
You are right.
In my case I obviously had corrupted the heap somewhere else - now it works as
expected.
Thanks for your quick answer,
Helmar
Am Donnerstag, 25. November 2010 16:11:03 schrieb Heikki Linnakangas:
> On 25.11.2010 13:45, Helmar Spangenberg wrote:
> > Bug reference: 5769
> > Log
"Helmar Spangenberg" writes:
> Referring to the manual, I can pfree the result returned by SPI_getvalue.
Well, the result is the output of a datatype output function. I think
that's palloc'd by all standard datatypes, but maybe you're working with
a custom datatype that tries to return a constan
"Martin Edlman" writes:
> I encountered this problem during migration of the database from PgSQL 8.4
> (where it works) to PgSQL 9.0.1.
For me, this example fails on both 8.4 and 9.0. It works on both after
removing the ill-considered quote_literal call here:
> INSERT INTO tmp.amavis_user
On 11/25/2010 12:28 PM, Darryl Pye wrote:
> PostgreSQL version: 9.01
32-bit or 64-bit ?
A single postgres process appears to be constantly growing in memory usage
until it reaches 100% of memory on the machine.
How are you watching it? Task manager?
You need to use something that can di
The following bug has been logged online:
Bug reference: 5771
Logged by: Shafqat Ali
Email address: shaf...@k5.com.au
PostgreSQL version: 8.3
Operating system: XP Professional SP3
Description:C:\Program Files\PostgreSQL\8.3\Data is not accessible.
Details:
After ins
10 matches
Mail list logo