[PATCHES] Better psql tab-completion support for schemas and tables

2007-10-21 Thread Greg Sabino Mullane
Full support for all schema and table name combinations when getting a list of attributes. All of the following will now work: select * from information_schema.columns where tab select * from foo where tab select * from user where tab select * from foo where tab select * from Uppercase.lower

Re: [PATCHES] Better psql tab-completion support for schemas and tables

2007-10-21 Thread Alvaro Herrera
Greg Sabino Mullane wrote: Full support for all schema and table name combinations when getting a list of attributes. All of the following will now work: diff -c please ... -- Alvaro Herrerahttp://www.CommandPrompt.com/ PostgreSQL Replication, Consulting,

[PATCHES] Better psql tab-completion support for schemas and tables

2007-10-21 Thread Greg Sabino Mullane
(oops, this time with -c, thanks Alvaro) Full support for all schema and table name combinations when getting a list of attributes. All of the following will now work: select * from information_schema.columns where tab select * from foo where tab select * from user where tab select * from foo

[PATCHES] Hash Index Build Patch v2

2007-10-21 Thread Tom Raney
This revised version of our patch uses the function estimate_rel_size() from plancat.c to estimate the number of tuples in the parent relation. This method is an alternative to scanning the parent relation to estimate the number of tuples, as we did in the first version of the patch. -Tom

[PATCHES] pgstattuple locking fix

2007-10-21 Thread ITAGAKI Takahiro
Here is a trivial fix of locking issue in pgstattuple(). It was locking buffers around PageGetHeapFreeSpace() in the heap scan loop, but not in the scanning of the tail. I think we need locks in the tail, too. Regards, --- ITAGAKI Takahiro NTT Open Source Software Center pgstattuple_lock.patch

Re: [PATCHES] pgstattuple locking fix

2007-10-21 Thread Tom Lane
ITAGAKI Takahiro [EMAIL PROTECTED] writes: Here is a trivial fix of locking issue in pgstattuple(). Hmm, is this really a bug, and if so how far back does it go? I'm thinking that having a pin on the buffer should be enough to call PageGetHeapFreeSpace. regards, tom lane