Skip site navigation (1) Skip section navigation (2)

Re: Pet Peeves?

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Pet Peeves?
Date: 2009-01-30 17:02:09
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-general
On 1/29/09, Gregory Stark <stark(at)enterprisedb(dot)com> wrote:
>  I'm putting together a talk on "PostgreSQL Pet Peeves" for discussion at
>  FOSDEM 2009 this year. I have a pretty good idea what some them are of course,

Here are couple of mine.  Had to dig a bit.  There may be some
duplication with others:

*) In place upgrade (everybody's #1)
*) lack of *generally usable* standalone mode which leads to:
*) libpq. needs rewrite: incorporate libpqtypes functionality, sane
error system, many other things.  would be nice to be able to use
libpq in standalone as described above.
*) update foo set foo = foo; doesn't work (currently thread on hackers)
*) named parameters in plain sql functions don't work
*) can't use insert/update returning in subquery (prob #3 requested
after IPU and hot standy)
*) stored procedures!! to some, this means multiset.  to me, it means
pl/pgsql without automatic transaction mgmt.  ideally, we get both
*) CTE expressions can't end in insert (slight variant of above)
*) no easy way to have database feed constants into 'create replace
function'  would be nice to have above take string expression, not
*) libpqtypes bumped to contrib :D
*) would be nice to run some arbitrary sql when session dumps.  only
possible today with highly circuitous on_proc_exit that connects back
to the database...ugh
*) listen/notify needs reworking
*) pl/sh should be raised to contrib at minimum. diamond in the rough

and my #1 pet peeve is <drumroll>:
*) having to answer questions about why count(*) is slow!


In response to

  • Pet Peeves? at 2009-01-29 13:16:17 from Gregory Stark


pgsql-general by date

Next:From: Craig RingerDate: 2009-01-30 17:06:50
Subject: Re: Pet Peeves?
Previous:From: Alvaro HerreraDate: 2009-01-30 17:01:10
Subject: Re: Pet Peeves?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group