Re: Nothing is using StrategyNotifyBgWriter() anymore

Answering my own question... I now see that the wakeup does in fact happen in StrategyGetBuffer(). Sorry for the noise. On 6/16/22, 5:32 PM, "Jim Nasby" wrote: While browsing through some of the clock-sweep code I noticed that the only place StrategyNotifyBgWriter() is called now is

Re: Problems with pg_upgrade and extensions referencing catalog tables/views

> On May 9, 2019, at 7:14 PM, Bruce Momjian wrote: > > On Wed, May 8, 2019 at 10:07:23PM +0000, Nasby, Jim wrote: >> I don’t recall why pg_upgrade wants to control OIDs… don’t we >> re-create all catalog entries for user objects from scratch? > > The C comment at t

Re: New EXPLAIN option: ALL

> On May 8, 2019, at 4:22 PM, Vik Fearing wrote: > > On 07/05/2019 09:30, David Fetter wrote: >> Folks, >> >> It can get a little tedious turning on (or off) all the boolean >> options to EXPLAIN, so please find attached a shortcut. > > I would rather have a set of gucs such as

Problems with pg_upgrade and extensions referencing catalog tables/views

pgTap has a view that references pg_proc; to support introspection of functions and aggregates. That view references proisagg in versions < 11, and prokind in 11+. pgtap's make process understands how to handle this; modifying the creation scripts as necessary. It actually has to do this for

Re: COPY FROM WHEN condition

On Oct 11, 2018, at 10:35 AM, David Fetter wrote: > >> It didn't get far, but you may want to take a look at a rejected patch for >> copy_srf() (set returning function) >> https://www.postgresql.org/message-id/CADkLM%3DdoeiWQX4AGtDNG4PsWfSXz3ai7kY%3DPZm3sUhsUeev9Bg%40mail.gmail.com >>

Re: Super PathKeys (Allowing sort order through precision loss functions)

> On Oct 30, 2018, at 9:08 AM, Simon Riggs wrote: > > On Tue, 30 Oct 2018 at 07:58, David Rowley > wrote: > > I've started working on something I've ended up calling "Super > PathKeys". The idea here is to increase the likelihood of a Path with > PathKeys being used for a purpose that

Re: PostgreSQL Limits and lack of documentation about them.

> On Oct 31, 2018, at 5:22 PM, David Rowley > wrote: > > On 1 November 2018 at 04:40, John Naylor wrote: >> Thanks for doing this. I haven't looked at the rendered output yet, >> but I have some comments on the content. >> >> + Maximum Relation Size >> + 32 TB >> + Limited by

Re: Create roles trigger

Please do not post to multiple lists. Moving -hackers to BCC. > On Sep 27, 2018, at 4:07 AM, Александр Аникин wrote: > > Hey, folks! > > I've got a question about events on roles creation. > > I need to execute some custom logic on role creation. > > All information about roles located in

Re: pgsql: Improve autovacuum logging for aggressive and anti-wraparound ru

> On Sep 24, 2018, at 1:29 PM, Andres Freund wrote: > > I'm very doubtful this is an improvement. Especially with the upcoming > pluggable storage work making vacuumlazy.c heap specific, while vacuum.c > stays generic. The concept of something like > PROC_VACUUM_FOR_WRAPAROUND, should imo not

Re: found xmin from before relfrozenxid on pg_catalog.pg_authid

On May 26, 2018, at 1:45 PM, Andres Freund wrote: > Does anybody see a way to not have to remove the .init file? How about only keeping the critical info for being able to find relations in the .init files, and then fully populate the cache by doing a normal lookup? Since