Cezio wrote post about removing elements from arrays in PostgreSQL.
Unfortunately his blog engine requires registration before comment, which I don't like, so I decided to comment using my own blogspace.
Tag: postgresql
Waiting for 8.4 – hash based DISTINCT
Today Tom Lane committed patch which gives DISTINCT ability to use hash aggregate – just like GROUP BY.
Waiting for 8.4 – RETURNS TABLE
Pavel Stehule wrote, and Tom Lane committed patch which ads new syntax for set-returning functions: “RETURNS TABLE".
Writing sprintf, and overcoming limitations in pl/perl
Having new VARIADIC functions, I decided it would be cool to be able to write sprintf() function.
Basically the idea is simple, plperl function, which takes “format", and list of arguments and returns generated output.
Continue reading Writing sprintf, and overcoming limitations in pl/perl
Waiting for 8.4 – variadic functions
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.
Waiting for 8.4 – storage types for table columns
Gregory Stark wrote, and Bruce Momjian committed (on 14th of July) patch which shows storage type in psql.
Continue reading Waiting for 8.4 – storage types for table columns
Waiting for 8.4 – sequence details
On 15th of July, Bruce Momjian commited patch written by Dickson S. Guedes, which:
Have psql \d show the value of sequence columns.
Suppressing CONTEXT lines in psql
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?
Who/what is trashing db performance?
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?
Conditional DDL?
Every now and then I see people ask the question – how to create table if it doesn't exist yet, how to drop it, but only if it does exist and so on.
Well, starting from 8.2 dropping should be not a problem anymore. But what about create? Alter?
Let's try to do it…