Re: [PATCH] New default role allowing to change per-role/database settings

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: Shinya11(dot)Kato(at)nttdata(dot)com
Cc: michael(dot)banck(at)credativ(dot)de, sfrost(at)snowman(dot)net, ibrar(dot)ahmad(at)gmail(dot)com, vignesh21(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] New default role allowing to change per-role/database settings
Date: 2022-01-14 10:12:49
Message-ID: 20220114101249.wdh2kuo5nog3zzxz@jrouhaud
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Wed, Sep 08, 2021 at 07:38:25AM +0000, Shinya11(dot)Kato(at)nttdata(dot)com wrote:
> >Thanks for letting me know, I've attached a rebased v4 of this patch, no other
> >changes.
> I tried it, but when I used set command, tab completion did not work properly and an error occurred.

Also, the patch doesn't apply anymore:

http://cfbot.cputube.org/patch_36_2918.log

=== Applying patches on top of PostgreSQL commit ID 5513dc6a304d8bda114004a3b906cc6fde5d6274 ===
=== applying patch ./v4-0001-Add-new-PGC_ADMINSET-guc-context-and-pg_change_ro.patch
[...]
1 out of 23 hunks FAILED -- saving rejects to file src/backend/utils/misc/guc.c.rej

I'm switching the patch to Waiting on Author.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabrice Chapuis 2022-01-14 10:17:07 Re: Logical replication timeout problem
Previous Message Sergey Shinderuk 2022-01-14 10:01:39 Re: Windows: Wrong error message at connection termination