Re: Proposal: roll pg_stat_statements into core - Mailing list pgsql-hackers

From David Fetter
Subject Re: Proposal: roll pg_stat_statements into core
Date
Msg-id 20190903233840.GH21153@fetter.org
Whole thread Raw
In response to Re: Proposal: roll pg_stat_statements into core  (Stephen Frost <sfrost@snowman.net>)
Responses Re: Proposal: roll pg_stat_statements into core
List pgsql-hackers
On Tue, Sep 03, 2019 at 03:56:28PM -0400, Stephen Frost wrote:
> Greetings,
> 
> * David Fetter (david@fetter.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..)

Agreed.

> 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?

Best,
David.
-- 
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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Proposal to suppress errors thrown by to_reg*()
Next
From: Stephen Frost
Date:
Subject: Re: Proposal: roll pg_stat_statements into core