Re: [BUGS] BUG #4916: wish: more statistical functions (median, percentiles etc)

2009-07-10 Thread Pavel Stehule
2009/7/11 Richard Neill : > > The following bug has been logged online: > > Bug reference:      4916 > Logged by:          Richard Neill > Email address:      rn...@cam.ac.uk > PostgreSQL version: 8.4 > Operating system:   Linux > Description:        wish: more statistical functions (median, percen

Re: [BUGS] BUG #4916: wish: more statistical functions (median, percentiles etc)

2009-07-10 Thread Richard Neill
Dear Joshua, Thanks for your reply. Sadly, I haven't the time (or expertise) to write this myself. However, the feature would be really useful to have. I'd certainly be willing to make a £200 payment or donation in return. I'm aware that this number is problematic, as it undervalues developer

Re: [BUGS] BUG #4916: wish: more statistical functions (median, percentiles etc)

2009-07-10 Thread Joshua Tolley
On Sat, Jul 11, 2009 at 02:12:22AM +0100, Richard Neill wrote: > Thanks for your reply. Sadly, I haven't the time (or expertise) to write > this myself. However, the feature would be really useful to have. I'd > certainly be willing to make a £200 payment or donation in return. That's very nic

Re: [BUGS] BUG #4916: wish: more statistical functions (median, percentiles etc)

2009-07-10 Thread Joshua Tolley
On Fri, Jul 10, 2009 at 11:37:46PM +, Richard Neill wrote: > In addition to the existing aggregate functions (avg, stddev etc), it would > be nice if postgres could return further information. For example, the > quartiles, percentiles, and median. > > [mode would also be useful, as an expli

[BUGS] BUG #4916: wish: more statistical functions (median, percentiles etc)

2009-07-10 Thread Richard Neill
The following bug has been logged online: Bug reference: 4916 Logged by: Richard Neill Email address: rn...@cam.ac.uk PostgreSQL version: 8.4 Operating system: Linux Description:wish: more statistical functions (median, percentiles etc) Details: In addition to the e

Re: [BUGS] BUG #4913: Row missing from primary key index

2009-07-10 Thread Mathieu De Zutter
On Fri, Jul 10, 2009 at 6:24 PM, Tom Lane wrote: > As far as anyone knows, it's impossible to get into the > disconnected-backends state unless (a) you manually remove the > postmaster.pid file that provides the interlock against it, or > (b) you're trying to run multiple copies of Postgres on di

Re: [BUGS] BUG #4914: uuid_generate_v4 not present in eithersource or yum/rpm

2009-07-10 Thread Alvaro Herrera
Dan Boeriu wrote: > Could you please tell me how you installed it? What exact version did you > download? Was it source or yum/rpm? > I tried both with source compiling with the flags for oops-uuid and still > didn't get the function uuid_generate_v4. > > If you installed from source please send

Re: [BUGS] BUG #4913: Row missing from primary key index

2009-07-10 Thread Tom Lane
Mathieu De Zutter writes: > $ sudo ipcs -m > -- Shared Memory Segments > keyshmid owner perms bytes nattch status > 0x0052e2c1 1081344postgres 60030384128 21 > 0x 425985 postgres 60018440 34 > 0x 458754

Re: [BUGS] BUG #4913: Row missing from primary key index

2009-07-10 Thread Mathieu De Zutter
On Fri, Jul 10, 2009 at 5:03 PM, Tom Lane wrote: > This could be checked by looking at the output of "ipcs -m" > (run this as root to be sure you get everything). > $ sudo ipcs -m -- Shared Memory Segments keyshmid owner perms bytes nattch statu

Re: [BUGS] BUG #4913: Row missing from primary key index

2009-07-10 Thread Tom Lane
Mathieu De Zutter writes: > On Fri, Jul 10, 2009 at 2:02 AM, Alvaro Herrera > wrote: >> What do the INSERT lines look like? > * This is the INSERT query, called from PHP/Apache > INSERT INTO log_event (user_id, ip, action_id, object1_id, object2_id, > event_timestamp) > VALUES ($1, $2, $3, $4, $

Re: [BUGS] BUG #4913: Row missing from primary key index

2009-07-10 Thread Mathieu De Zutter
On Fri, Jul 10, 2009 at 2:02 AM, Alvaro Herrera wrote: > What do the INSERT lines look like? Is it a trigger, an insert called > directly by the application? How is the sequence involved -- lastval(), > nextval(), does the code just leave the column out for the default to fire? > > * This is th