| From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Richard Guo <guofenglinux(at)gmail(dot)com>, Japin Li <japinli(at)hotmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Replace (GUC_UNIT_MEMORY | GUC_UNIT_TIME) with GUC_UNIT in guc.c |
| Date: | 2023-06-15 08:06:56 |
| Message-ID: | CAD21AoDxEBXwY=tbePez96_56ud4J+DJ+oxmbOczncfX3KyJJw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jun 15, 2023 at 11:02 AM Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
>
> On Wed, Jun 14, 2023 at 4:47 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> >
> > On Wed, Jun 14, 2023 at 03:38:10PM +0800, Richard Guo wrote:
> > > +1. BTW, it seems that GUC_UNIT_TIME is not used anywhere except in
> > > GUC_UNIT. I was wondering if we can retire it, but maybe we'd better
> > > not. It still indicates that we need to use time units table.
> >
> > Some out-of-core code declaring custom GUCs could rely on that, so
> > it is better not to remove it.
>
> +1 not to remove it.
>
> I've attached the patch to fix (GUC_UNIT_MEMORY | GUC_UNIT_TIME)
> thing, and am going to push it later today to only master branch.
Pushed.
Regards,
--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sho Kato (Fujitsu) | 2023-06-15 08:07:19 | Fix a typo in rewriteHandler.c |
| Previous Message | Joel Jacobson | 2023-06-15 08:06:40 | Re: Do we want a hashset type? |