Re: Report oldest xmin source when autovacuum cannot remove tuples - Mailing list pgsql-hackers

From Scott Ray
Subject Re: Report oldest xmin source when autovacuum cannot remove tuples
Date
Msg-id GhIqK8CfmeX-u9drRyP0V0gBMYk0SO6dMHYW-woGxASgasMOG6nK_K6tMCYqIc_jkelCvF1RRScvQ7UHkDzSeJgIxKOY2CO1lJBJLulrbzg=@scottray.io
Whole thread
In response to Re: Report oldest xmin source when autovacuum cannot remove tuples  (Shinya Kato <shinya11.kato@gmail.com>)
List pgsql-hackers
> > Shinya said [1] that we could have a view in the future.  We could
> > have both the logging and the view call a single function that reads
> > the procArray and other sources to gather the horizon information.  I
> > think the logging and the view would complement each other.
> >
> > Should I start another thread?
>

> My mild preference would be to keep the discussion on this thread,
> since the shared function design is central to both the log and the
> view and may be easier to keep aligned in one place. That said, I'm
> not strongly attached to that, so please pick whichever feels more
> convenient.

I attached a patch that uses a helper function that could also be used
for a view, but I don't think it's necessary immediately, because
refactoring later wouldn't be difficult.

--
Scott Ray
Attachment

pgsql-hackers by date:

Previous
From: Alexander Nestorov
Date:
Subject: Re: [PATCH] btree_gist: add cross-type integer operator support for GiST
Next
From: Scott Ray
Date:
Subject: Re: [PATCH] Don't call ereport(ERROR) from recovery target GUC assign hooks