Re: [PATCHES] pg_regress in C

2006-08-18 Thread Magnus Hagander
Per discussion at the conference: In order to run the regression tests on Windows without msys, pg_regress needs to be reimplemnted in C. This has some minor portability issues (macros with ... aren't portable, for instance) but I think it's something we need to do. Barring objections

Re: [HACKERS] [PATCHES] selecting large result sets in psql using

2006-08-18 Thread Peter Eisentraut
Am Donnerstag, 17. August 2006 20:05 schrieb Chris Mair: \gc sounds like a good idea to me :) Strictly speaking, in the randomly defined grammer of psql, \gc is \g with an argument of 'c' (try it, it works). I'm not sure what use case you envision for this feature. Obviously, this is for

[PATCHES] Information_schema fixes for sequences and temporary tables

2006-08-18 Thread Greg Sabino Mullane
More to come, but these two are probably worth backpatching. Sequences were not being shown due to the use of lowercase 's' instead of 'S', and the views were not checking for table visibility with regards to temporary tables and sequences. -- Greg Sabino Mullane [EMAIL PROTECTED] End Point

Re: [PATCHES] Information_schema fixes for sequences and temporary tables

2006-08-18 Thread Tom Lane
Greg Sabino Mullane [EMAIL PROTECTED] writes: More to come, but these two are probably worth backpatching. We can't really backpatch changes to information_schema, since we can't force initdb in back branches. I'd be interested to see you cite chapter and verse in the SQL spec where it says

[PATCHES] Information schema - finalize key_column_usage

2006-08-18 Thread Greg Sabino Mullane
Correctly populates the position_in_unique_constraint column in the information_schema.key_column_usage view. -- Greg Sabino Mullane [EMAIL PROTECTED] End Point Corporation PGP Key: 0x14964AC8 200608182231 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 Index:

Re: [PATCHES] Information_schema fixes for sequences and temporary tables

2006-08-18 Thread Greg Sabino Mullane
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'd be interested to see you cite chapter and verse in the SQL spec where it says that information_schema should hide temp tables of other backends. That change seems pretty dubious to me. (More likely, we should be adding tests on whether the