Re: What is the difference between context of "sighup", "super-backend", and "backend" in pg_settings?

On Sat, Jun 26, 2021 at 12:56:21PM +0800, 周书林 wrote: > Hi, > > I am interested in the configuration parameter of Postgres. I found that > the configuration parameters in context of "sighup", "super-backend", and > "backend" are all required to send "SIGHUP" signal to postmaster for > rereading con

What is the difference between context of "sighup", "super-backend", and "backend" in pg_settings?

Hi, I am interested in the configuration parameter of Postgres. I found that the configuration parameters in context of "sighup", "super-backend", and "backend" are all required to send "SIGHUP" signal to postmaster for rereading configuration files. So my question is, what is the difference betwe

Re: Difference between text_pattern_ops and varchar_pattern_ops

David Morgenstern writes: > Can somebody explain why text_pattern_ops can be used on varchar > columns, considering it can’t be used for bpchar columns? The underlying rule there is that an opclass can be applied to an index column if the column's actual type is binary-coercible to what the opcla

Re: Difference between text_pattern_ops and varchar_pattern_ops

On Fri, 2021-06-25 at 12:29 +0200, David Morgenstern wrote: > The documentation for operator classes > (https://www.postgresql.org/docs/current/indexes-opclass.html) > seems to indicate that text_pattern_ops should only be used for text columns > and varchar_pattern_ops should be used for varcha

Difference between text_pattern_ops and varchar_pattern_ops

Hello all, The documentation for operator classes (https://www.postgresql.org/docs/current/indexes-opclass.html ) seems to indicate that text_pattern_ops should only be used for text columns and varchar_pattern_ops should be used fo

Re: pg_dump/pg_restore vs default_transaction_read_only under PG 13.2

Am Fri, Jun 25, 2021 at 11:39:46AM +0200 schrieb Karsten Hilbert: > I would be happy to hope that pg_dump might ... > gain a --do-not-alter-database-to-read-only or even a --(pre|post)-dump-sql=(pre|post).sql allowing for (here) temporarily altering a role to default_transaction_read_only=off/on

Re: pg_dump/pg_restore vs default_transaction_read_only under PG 13.2

> >And this is the restore: > > > sudo -u postgres psql -d postgres -f create_database.sql > > sudo -u postgres pg_restore --verbose --create --dbname=template1 > > --exit-on-error -p ${GM_PORT} ${BACKUP}.dir/ > Remove --create and change dbname to the database name from > creat