Pavel Stehule wrote, and then Tom Lane committed (on 16th of July), patch which adds to PostgreSQL support for functions with variable number of arguments.
Gregory Stark wrote, and Bruce Momjian committed (on 14th of July) patch which shows storage type in psql.
On 15th of July, Bruce Momjian commited patch written by Dickson S. Guedes, which:
Have psql \d show the value of sequence columns.
Sorry for delay in writing new posts – especially new information about “what's new in pg 8.4".
I've been on vacation, and crashed my car. New posts will be coming this week – for starters – I have 244 unread mails from pg-committers mailing list, so you can expect at least couple of new things in 8.4 🙂
CONTEXT messages are quite informative, but when you don't need them, they can be real pain in the eyes:
psql:trees.sql:68: NOTICE: Adding tree structures to table public.testit. CONTEXT: SQL function "add_tree_structure" statement 1 psql:trees.sql:68: NOTICE: Tree table will be public.testit_tree. CONTEXT: SQL function "add_tree_structure" statement 1 psql:trees.sql:68: NOTICE: Primary key in source table is: id CONTEXT: SQL function "add_tree_structure" statement 1
I mean – I know the context. I'm writing the sql file right now, how to disable it?
Every so often I need to find who exactly is damaging database performance. I mean – I have db connection which does something strange/wrong with the database, but what exactly is responsible?
Switching to separate user for every program, script and developer would solve the problem, but it is not always an option. So, what should I do?