| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Hubert Zhang <hzhang(at)pivotal(dot)io> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Heikki Linnakangas <hlinnakangas(at)pivotal(dot)io> |
| Subject: | Re: Control your disk usage in PG: Introduction to Disk Quota Extension |
| Date: | 2019-02-16 04:53:51 |
| Message-ID: | 20190216045351.q344ex2utwk7ndtr@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2019-01-30 10:26:52 +0800, Hubert Zhang wrote:
> Hi Michael, Robert
> For you question about the hook position, I want to explain more about the
> background why we want to introduce these hooks.
> We wrote a diskquota extension <https://github.com/greenplum-db/diskquota>
> [ ...]
> On Tue, Jan 22, 2019 at 12:08 PM Hubert Zhang <hzhang(at)pivotal(dot)io> wrote:
>
> > > For this particular purpose, I don't immediately see why you need a
> >> > hook in both places. If ReadBuffer is called with P_NEW, aren't we
> >> > guaranteed to end up in smgrextend()?
> >> Yes, that's a bit awkward.
Please note that on PG lists the customary and desired style is to quote
inline in messages rather than top-quote.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-02-16 05:12:39 | Re: SQL/JSON: functions |
| Previous Message | Andres Freund | 2019-02-16 04:10:26 | Re: [PATCH v20] GSSAPI encryption support |