[BUGS] BUG #8380: initdb ignore options

2013-08-10 Thread karsten . lenz
The following bug has been logged on the website: Bug reference: 8380 Logged by: Karsten Lenz Email address: karsten.l...@gmx.ch PostgreSQL version: 9.2.4 Operating system: CentOS 6.4 Description: Hello, initdb is ignoring the options, i wnt install with differend d

Re: [BUGS] pg_stat_statements produces multiple entries for a single query with track = 'top'

2013-08-10 Thread Peter Geoghegan
On Sat, Aug 10, 2013 at 5:45 PM, Tom Lane wrote: > Isn't this just the behavior we decided we wanted for SQL-language > functions? At least, if we change pg_stat_statements so it doesn't > break out SQL-language functions, I'm sure somebody's gonna complain. Perhaps there was some discussion of

Re: [BUGS] pg_stat_statements produces multiple entries for a single query with track = 'top'

2013-08-10 Thread Tom Lane
Peter Geoghegan writes: > So with this single earthdistance query, there are multiple > invocations of the executor, and thus multiple associated > pg_stat_statements entries (one with 4 "calls"). Isn't this just the behavior we decided we wanted for SQL-language functions? At least, if we chang

[BUGS] pg_stat_statements produces multiple entries for a single query with track = 'top'

2013-08-10 Thread Peter Geoghegan
While at 2ndQuadrant, I was responsible for a project called pg_stat_plans, which as some people subscribed to this mailing list will be aware is essentially a tool for instrumenting Postgres query execution costs at the plan granularity rather than at the query granularity. It is derivative of pg_