Re: Publish autovacuum informations

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Publish autovacuum informations
Date: 2015-01-05 16:44:13
Message-ID: CAECtzeWkxwqcAE5VfzkSjk44Xsa0GdTL36d9UaHNvVQ-cG-9xg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2015-01-05 17:40 GMT+01:00 Robert Haas <robertmhaas(at)gmail(dot)com>:

> On Wed, Dec 31, 2014 at 12:46 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > I'd be all right with putting the data structure declarations in a file
> > named something like autovacuum_private.h, especially if it carried an
> > annotation that "if you depend on this, don't be surprised if we break
> > your code in future".
>
> Works for me. I am not in general surprised when we do things that
> break my code, or anyway, the code that I'm responsible for
> maintaining. But I think it makes sense to segregate this into a
> separate header file so that we are clear that it is only exposed for
> the benefit of extension authors, not so that other things in the core
> system can touch it.
>
>
I'm fine with that too. I'll try to find some time to work on that.

Thanks.

--
Guillaume.
http://blog.guillaume.lelarge.info
http://www.dalibo.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2015-01-05 16:45:22 Re: [COMMITTERS] pgsql: Change how first WAL segment on new timeline after promotion is
Previous Message Robert Haas 2015-01-05 16:40:20 Re: Publish autovacuum informations