[BUGS] BUG #2502: PQclear: "invalid next size"

The following bug has been logged online: Bug reference: 2502 Logged by: J. R. Fisher Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1 Operating system: Linux Description:PQclear: "invalid next size" Details: One patch of C++, two programs using it. One prog

[BUGS] BUG #2504: Major MS SQL Server bug

The following bug has been logged online: Bug reference: 2504 Logged by: Email address: [EMAIL PROTECTED] PostgreSQL version: MS SQL 2000 Operating system: WIndows Description:Major MS SQL Server bug Details: See http://groups.google.com/group/microsoft.public.sqls

[BUGS] BUG #2505: Translations error in pgAdmin III

The following bug has been logged online: Bug reference: 2505 Logged by: Wolfgang Bansa Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1.4 Operating system: Win XP Prof SP2 Description:Translations error in pgAdmin III Details: pgAdmin III Version 1.4.2 (Mar

[BUGS] BUG #2503: Query results differ based on record count of unrelated table.

The following bug has been logged online: Bug reference: 2503 Logged by: Russell Francis Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1.4 Operating system: FreeBSD 6.1 Description:Query results differ based on record count of unrelated table. Details: Summ

Re: [BUGS] BUG #2503: Query results differ based on record count of unrelated table.

Russell Francis wrote: > If a SELECT statement contains a table in it's FROM clause which has 0 > records in it, the query will not return any results. If a record is added > to the table even though it shouldn't modify the results of query, the query > will return the expected result. > > The S

Re: [BUGS] BUG #2502: PQclear: "invalid next size"

"J. R. Fisher" <[EMAIL PROTECTED]> writes: > *** glibc detected *** free(): invalid next size (normal): 0x08068ab0 Sounds like a memory clobber. The odds are extremely high that the clobber is in your own code, not libpq. If nothing else comes to mind, you could probably use ElectricFence or som