Re: pg_wal directory max size

On 22 December 2022 04:00:57 CET, Yi Sun wrote: >Hello guys, > >We are planning the server disk space, pg_wal directory max size is wal >file size*wal_keep_segments? or is it also decided by other parameters >please? We tried to search for this, but could not find the answer > >For example our pos

Re: pg_wal directory max size

On 22 December 2022 04:00:57 CET, Yi Sun wrote: >Hello guys, > >We are planning the server disk space, pg_wal directory max size is wal >file size*wal_keep_segments? or is it also decided by other parameters >please? We tried to search for this, but could not find the answer > >For example our pos

Re: Implementing foreign data wrappers and avoiding n+1 querying

On Thu, 22 Dec 2022 at 13:31, David Gilman wrote: > > When a fdw table participates in query planning and finds itself as > part of a join it can output a parameterized path. If chosen, Postgres > will dutifully call the fdw over and over via IterateForeignScan to > fetch matching tuples. Many fdw

pg_wal directory max size

Hello guys, We are planning the server disk space, pg_wal directory max size is wal file size*wal_keep_segments? or is it also decided by other parameters please? We tried to search for this, but could not find the answer For example our postgresql is 9.6 below parameters value, is the pg_wal dir

Re: tsvector not giving expected results on one host

Oleg Bartunov wrote on 12/21/22 12:31 PM: I On Wed, Dec 21, 2022 at 1:12 PM Oleg Bartunov wrote: Dan, it's always good to specify configuration name in a query to avoid recheck, since websearch_to_tsquery(regconfig, text) is immutable, while websearch_to_tsquery(text) is stable. I am glad

Implementing foreign data wrappers and avoiding n+1 querying

When a fdw table participates in query planning and finds itself as part of a join it can output a parameterized path. If chosen, Postgres will dutifully call the fdw over and over via IterateForeignScan to fetch matching tuples. Many fdw extensions do network traffic, though, and it would be benef

Re: Regd. the Implementation of Wallet (in Oracle) config equivalent in postgreSQL whilst the database migration

Yea. I wasn't clear. I tar up the dump files as part of the command. Dont lose your keys is awesome in theory. AWS comes with managed keys. The Wal command will let you encrypt your Wal files too but if I were a hacker then I would also copy ssh folders. It depends on security and business needs. I

Re: Regd. the Implementation of Wallet (in Oracle) config equivalent in postgreSQL whilst the database migration

And encrypting a tar.gz file presumes a pretty small database.  (The --jobs= option was added to pg_dump/pg_restore for just that reason.) On 12/21/22 16:25, Benedict Holland wrote: What would you be missing? You can encrypt databases. You can encrypt the s3 buckets using kms. You can govern ac

Re: Regd. the Implementation of Wallet (in Oracle) config equivalent in postgreSQL whilst the database migration

If a hacker gets in with root access, they can copy /your/ (and my) Postgresql database files (or, more easily, the backup files) off site, restore them, and then have access to your database.  Not so much TDE-encrypted databases, since the backups are encrypted too and you need the key to decr

Re: Regd. the Implementation of Wallet (in Oracle) config equivalent in postgreSQL whilst the database migration

What would you be missing? You can encrypt databases. You can encrypt the s3 buckets using kms. You can govern access via ssh Auth. When you do backups, you can encrypt the tar.gz files or whatever format and store it on s3. Same with the wal files. The fact that oracle charges for this is a joke.

Re: Regd. the Implementation of Wallet (in Oracle) config equivalent in postgreSQL whilst the database migration

> Am 21.12.2022 um 22:34 schrieb Laurenz Albe : > > There is no exact equivalent, but there is something similar and much better: > you can > authenticate the client with SSL client certificates: > https://www.postgresql.org/docs/current/auth-cert.html >

Re: Regd. the Implementation of Wallet (in Oracle) config equivalent in postgreSQL whilst the database migration

On Wed, 2022-12-21 at 04:48 +, Chetan Kosanam wrote: > We are operating within one of the AWS business units ofTCS. Our team is > working on > the Database migration from Oracle(on Amazon EC2) to PostgreSQL. The reason > for this > e-mailer is to seek your earnest required support from you on

New setup of pgadmin4 with kerberos not working

All - I am new to Postgres and Kerberos. That said, I built out Postgres db. I got a keytab file from AD. I'm sure it's all sorts of wonky but I did follow instructions and got guidance. Client based user authentication works from another linux server, after running kinit. What I can't get worki

Re: Regd. the Implementation of Wallet (in Oracle) config equivalent in postgreSQL whilst the database migration

I could find old post on postgres community , https://www.postgresql.org/message-id/20180625142233.GD20745%40momjian.us On Thu, May 17, 2018 at 07:07:00AM +, ROS Didier wrote: > Hi > > Regarding the encryption of data by pgcrypto, I would like to > know the recommendations for the management

Re: Regd. the Implementation of Wallet (in Oracle) config equivalent in postgreSQL whilst the database migration

śr., 21 gru 2022 o 18:33 Chetan Kosanam napisał(a): > TCS Confidential > > Hi *Support*@ *PostgreSQL* Team, > > > > *Greetings* *!!* > > > > We are operating within one of the *AWS business* units of *TCS*. Our > team is working on the *Database migration from Oracle(on Amazon EC2) to > PostgreS

Regd. the Implementation of Wallet (in Oracle) config equivalent in postgreSQL whilst the database migration

TCS Confidential Hi Support@ PostgreSQL Team, Greetings !! We are operating within one of the AWS business units of TCS. Our team is working on the Database migration from Oracle(on Amazon EC2) to PostgreSQL. The reason for this e-mailer is to seek your earnest required support from you on t

Re: tsvector not giving expected results on one host

I On Wed, Dec 21, 2022 at 1:12 PM Oleg Bartunov wrote: > > Dan, > > it's always good to specify configuration name in a query to avoid > recheck, since > websearch_to_tsquery(regconfig, text) is immutable, while > websearch_to_tsquery(text) is stable. immutable function calculates once in plann

Re: dropped default locale

Karsten Hilbert writes: > For that matter, is DELETE FROM pg_collation ... equivalent > to DROP COLLATION ? There's also entries in pg_depend and pg_shdepend to worry about. For these built-in collations, as of v15 there are no such entries, but prior versions had explicit "pin" entries.

Re: dropped default locale

Am Wed, Dec 21, 2022 at 03:46:48PM +0100 schrieb Karsten Hilbert: > I wasn't so sure whether inserting appropriate > rows would be equivalent to create collation... For that matter, is DELETE FROM pg_collation ... equivalent to DROP COLLATION ? Thanks, Karsten -- GPG 40BE 5B0E C98E 1713 AFA6 5

Re: dropped default locale

Am Wed, Dec 21, 2022 at 03:41:24PM +0100 schrieb Laurenz Albe: > I would definitely go for the backup, but here is how you can > create these three rows in PostgreSQL v15: > > INSERT INTO pg_collation > (oid, collname, collnamespace, collowner, collprovider, > collisdeterministic, colle

Re: dropped default locale

On Wed, 2022-12-21 at 15:24 +0100, Karsten Hilbert wrote: > I managed to drop the "special" collations default, C, and > POSIX with OIDs 100, 950, 951. > > Is there a way to recreate them (short of restoring a backup) > ? Naive attempts with create collation do not seem to work > out. I would def

dropped default locale

Dear all, I managed to drop the "special" collations default, C, and POSIX with OIDs 100, 950, 951. Is there a way to recreate them (short of restoring a backup) ? Naive attempts with create collation do not seem to work out. Thanks, Karsten -- GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F

Re: tsvector not giving expected results on one host

Dan, it's always good to specify configuration name in a query to avoid recheck, since websearch_to_tsquery(regconfig, text) is immutable, while websearch_to_tsquery(text) is stable. See the difference: [local]:5433 oleg@oleg=# explain (analyze,costs off) select title from apod where websearc