|From:||David Fetter <david(at)fetter(dot)org>|
|To:||Stephen Frost <sfrost(at)snowman(dot)net>|
|Cc:||PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: Proposal: roll pg_stat_statements into core|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On Tue, Sep 03, 2019 at 03:56:28PM -0400, Stephen Frost wrote:
> * David Fetter (david(at)fetter(dot)org) wrote:
> > I'd like to $Subject, on by default, with a switch to turn it off for
> > those really at the outer edges of performance. Some reasons include:
> Sure, half of contrib should really be in core (amcheck, file_fdw,
> postgres_fdw, maybe dblink, pageinspect, pg_buffercache,
> pg_freespacemap, pgstattuple, pg_visibility, sslinfo, maybe pgtrgm..)
> but we simply haven't got great facilities for either migrating those
> things into core (particularly during an upgrade..)
So a process that makes transitioning from extension to core in a(n at
least largely) mechanical way sounds like a Useful Thing™.
Would that be worth a separate thread once this CF is over?
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
|Next Message||Stephen Frost||2019-09-03 23:41:00||Re: Proposal: roll pg_stat_statements into core|
|Previous Message||Tom Lane||2019-09-03 22:56:59||Re: Proposal to suppress errors thrown by to_reg*()|