From: | Loles <lolesft(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | Dilip Kumar <dilipbalaut(at)gmail(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: |
Date: | 2021-05-17 07:32:27 |
Message-ID: | CA+FWGK414MMDomSD3bfZv=XpEnEF1Bq1twYO2=9CgV5zvgt1-w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Ok, now I know.
Thank you very much to all!!
El lun, 17 may 2021 a las 8:37, David G. Johnston (<
david(dot)g(dot)johnston(at)gmail(dot)com>) escribió:
> On Sunday, May 16, 2021, Loles <lolesft(at)gmail(dot)com> wrote:
>
>> I don't understand why the server starts that process if I'm not using
>> replication of any kind.
>>
>>
>> The server starts it with the default configuration of version 13.
>>
>> I think that it consumes resources that I do not need because, as I have
>> commented, I will not use replication of any kind.
>>
>
> It starts the process because at any time someone can execute a “create
> subscription” command. If no one does so the amount of time spent
> confirming the subscriptions table is empty is trivial.
>
> So, yes, it consumes resources. A minimal amount, likely not enough to
> spend time figuring out how to avoid and risking a change to the basic
> operational mode of the subsystem.
>
> David J.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | hamann.w | 2021-05-17 13:27:40 | unicode match normal forms |
Previous Message | David G. Johnston | 2021-05-17 06:37:29 | Re: |