Re: [BUGS] BUG #1006: information schema constraint information.
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes: > [ information_schema.constraint_column_usage gives wrong answers ] I think this part of the view's definition: AND (CASE WHEN c.contype = 'f' THEN c.confkey[pos.n] = a.attnum ELSE c.conkey[pos.n] = a.attnum END) should just be AND c.conkey[pos.n] = a.attnum The confkey array shows column numbers of the referenced columns, which is not the right thing to look at. If the view were also supposed to show referenced columns, then I think we'd need an additional UNION arm that joined on confrelid and confkey[] instead of conrelid/conkey[]. But if I read SQL99 correctly, only referencing not referenced columns are supposed to be shown. BTW, I also recommend deleting the clause AND a.attnum > 0 since for instance a UNIQUE constraint on the OID column is legitimate. Peter, does this change look right to you? regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [BUGS] libpq3 + ssl memory leak
Neil Conway <[EMAIL PROTECTED]> writes: > This fix needs to be in 7.4.1, so if anyone wants to review this > patch, that would be great. Looks reasonable from here, but confirmation from the complainant that it fixes his problem would be real good ... > P.S. I added an assertion in the backend code to help catch any other > memory leaks in this area. I didn't add an equivalent one to the > frontend code, because libpq doesn't seem to be setup for > assertions. Yeah, we can't assume that a decent support mechanism exists in an arbitrary client application. > When this is applied to 7.4.1, we probably shouldn't > include the assertion at the risk of suffering backend crashes. Assert away. People who are concerned about assertions destabilizing their systems don't build with asserts enabled in the first place. regards, tom lane ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[BUGS] BUG #1007: error during installation
The following bug has been logged online: Bug reference: 1007 Logged by: Wong Choon Hen Email address: [EMAIL PROTECTED] PostgreSQL version: 7.4 Operating system: Windows XP Description:error during installation Details: When running the following command as instructed:- nmake -f win32.mak I got the error message as follows:- This application has failed to start because mspdb71.dll was not found. Re-installing the application may fix this problem. Please advise. Thanks & regards ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [BUGS] BUG #1007: error during installation
PostgreSQL Bugs List wrote: This application has failed to start because mspdb71.dll was not found. Re-installing the application may fix this problem. This has nothing to do with Postgres. "mspdb71.dll" is part of Visual Studio .Net -- look in: "c:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE". More than likely you neglected to run vsvars32.bat to set up your environment correctly. HTH, Joe ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
