Re: Help needed for the resolution of memory leak

2024-01-17 Thread Sasmit Utkarsh
ok Thanks Merlin, I will go through the above specified doc and get back in case of further questions Regards, Sasmit Utkarsh +91-7674022625 On Thu, Jan 18, 2024 at 6:36 AM Merlin Moncure wrote: > On Wed, Jan 17, 2024 at 1:14 PM Sasmit Utkarsh > wrote: > >> Hi Merlin et al. >> >> Below are

Re: Moving to Postgresql database

2024-01-17 Thread Merlin Moncure
On Tue, Jan 16, 2024 at 11:05 AM Dominique Devienne wrote: > On Tue, Jan 16, 2024 at 5:07 PM Adrian Klaver > wrote: > >> On 1/16/24 00:06, Dominique Devienne wrote: >> > On Mon, Jan 15, 2024 at 5:17 AM veem v > > > wrote: >> > Is any key design/architectural

Re: Help needed for the resolution of memory leak

2024-01-17 Thread Merlin Moncure
On Wed, Jan 17, 2024 at 1:14 PM Sasmit Utkarsh wrote: > Hi Merlin et al. > > Below are some couple of observations attached as an "overview_of_code" > and other attachments "function_def_other_details" and leak sanitizer > report. Please assist with some clarifications given in overview_of_code

Re: undefined symbol when installing pgcrypto on 16.1

2024-01-17 Thread Michael Nolan
On Wed, Jan 17, 2024 at 5:32 PM Daniel Gustafsson wrote: > > > On 18 Jan 2024, at 00:24, Michael Nolan wrote: > > > > Sorry for the delay in responding, network issues kept me offline for > > several days. > > > > These are the openssl packages installed from the Almalinux 9 repositories: > > >

Re: undefined symbol when installing pgcrypto on 16.1

2024-01-17 Thread Daniel Gustafsson
> On 18 Jan 2024, at 00:24, Michael Nolan wrote: > > Sorry for the delay in responding, network issues kept me offline for > several days. > > These are the openssl packages installed from the Almalinux 9 repositories: > > apr-util-openssl.x86_64 1.6.1-23.el9 >

Re: undefined symbol when installing pgcrypto on 16.1

2024-01-17 Thread Michael Nolan
Sorry for the delay in responding, network issues kept me offline for several days. These are the openssl packages installed from the Almalinux 9 repositories: apr-util-openssl.x86_64 1.6.1-23.el9 @appstream openssl.x86_641:3.0.7-24.el9

Re: Moving to Postgresql database

2024-01-17 Thread Jim Nasby
On 1/17/24 5:31 AM, Dominique Devienne wrote: Is the pg_statement_rollback technically wrong? Can't what it does be done better and more efficiently if it was in the core itself? Is it a lot of code? I took a quick look at that extension, and it's doing pretty much what you'd do if this was

Re: postgres sql assistance

2024-01-17 Thread Jim Nasby
On 1/16/24 10:04 PM, arun chirappurath wrote: Architect is pressing for a native procedure to data load. It's possible to write a loader in pl/pgsql but it would be easily twice as complex as where you got on your first attempt. It would also never perform anywhere near as well as a

Re: pg_basebackup Restore problem

2024-01-17 Thread Johnathan Tiamoh
Thank You very much for your time. On Wed, Jan 17, 2024 at 4:51 PM Ron Johnson wrote: > Perfectly understandable, but tar *did* fail. Time to start debugging > your shell script. > > On Wed, Jan 17, 2024 at 4:26 PM Johnathan Tiamoh < > johnathantia...@gmail.com> wrote: > >> Ok. >> >> I'm a

Re: pg_basebackup Restore problem

2024-01-17 Thread Ron Johnson
Perfectly understandable, but tar *did* fail. Time to start debugging your shell script. On Wed, Jan 17, 2024 at 4:26 PM Johnathan Tiamoh wrote: > Ok. > > I'm a little confused because has always work > > On Wed, Jan 17, 2024 at 4:11 PM Ron Johnson > wrote: > >> Then you've got a bug

Re: pg_basebackup Restore problem

2024-01-17 Thread Johnathan Tiamoh
Ok. I'm a little confused because has always work On Wed, Jan 17, 2024 at 4:11 PM Ron Johnson wrote: > Then you've got a bug somewhere in: > tar -h -zxvf $PATH_FOLDER/* .tar.gz > ls $PATH_FOLDER/*.tar.gz | xargs -I {} tar -h -zxvf {} > > On Wed, Jan 17, 2024 at 4:07 PM Johnathan Tiamoh

Re: pg_basebackup Restore problem

2024-01-17 Thread Ron Johnson
Then you've got a bug somewhere in: tar -h -zxvf $PATH_FOLDER/* .tar.gz ls $PATH_FOLDER/*.tar.gz | xargs -I {} tar -h -zxvf {} On Wed, Jan 17, 2024 at 4:07 PM Johnathan Tiamoh wrote: > Yes. > > I am trying to restore the backups on a standby > > On Wed, Jan 17, 2024 at 4:04 PM Ron

Re: pg_basebackup Restore problem

2024-01-17 Thread Johnathan Tiamoh
Yes. I am trying to restore the backups on a standby On Wed, Jan 17, 2024 at 4:04 PM Ron Johnson wrote: > Wait a minute... *tar* is throwing the errors, not pg_basebackup, no? > > On Wed, Jan 17, 2024 at 3:27 PM Johnathan Tiamoh < > johnathantia...@gmail.com> wrote: > >> 1. What's in

Re: pg_basebackup Restore problem

2024-01-17 Thread Ron Johnson
Wait a minute... *tar* is throwing the errors, not pg_basebackup, no? On Wed, Jan 17, 2024 at 3:27 PM Johnathan Tiamoh wrote: > 1. What's in $PATH_FOLDER? > > /tnt/backup/current > > 2. What pg_basebackup command did you use? > > pg_basebackup -D "$baseback_dir" --format=tar \ >

Re: unbale to list schema

2024-01-17 Thread Erik Wienhold
On 2024-01-17 19:46 +0100, Atul Kumar wrote: > I am not able to find any solution to list all schemas in all databases at > once, to check the structure of the whole cluster. You have to connect to each database and run the necessary statements per database. > As I need to give a few privileges

Re: pg_basebackup Restore problem

2024-01-17 Thread Johnathan Tiamoh
1. What's in $PATH_FOLDER? /tnt/backup/current 2. What pg_basebackup command did you use? pg_basebackup -D "$baseback_dir" --format=tar \ "${comp_opts[@]}" --wal-method=stream --no-password --verbose "${PG_DUMP_OPTS[@]}" /bin/mv "$baseback_dir"/*

unbale to list schema

2024-01-17 Thread Atul Kumar
Hi, I am not able to find any solution to list all schemas in all databases at once, to check the structure of the whole cluster. As I need to give a few privileges to a user to all databases, their schemas and schemas' objects (tables sequences etc.). Please let me know if there is any

RE: Initiate backup from routine?

2024-01-17 Thread Kamil ADEM
Hello Troels, You can use the following statements in a procedure/function: CREATE TEMPORARY TABLE tt_cmdout(cmdoutput text); COPY tt_cmdout(cmdoutput) FROM PROGRAM 'pg_dump.exe '; But note that the user must have SUPERUSER or BYPASSRLS privileges or must be table owner. Ragards, Kamil Adem

Re: pg_basebackup Restore problem

2024-01-17 Thread Ron Johnson
1. What's in $PATH_FOLDER? 2. What pg_basebackup command did you use? 3. Why aren't you letting pg_basebackup maintain the WAL files it needs? On Wed, Jan 17, 2024 at 11:27 AM Johnathan Tiamoh wrote: > You need to tell us the PG version number *and* show us the full command > you ran. ? > >

Re: pg_basebackup Restore problem

2024-01-17 Thread Johnathan Tiamoh
You need to tell us the PG version number *and* show us the full command you ran. ? Postgresql Version 14.10 tar -h -zxvf $PATH_FOLDER/* .tar.gz ls $PATH_FOLDER/*.tar.gz | xargs -I {} tar -h -zxvf {} What user are you running pg_basebackup as? I ran it as postgres and now I'm restoring

Re: Initiate backup from routine?

2024-01-17 Thread Ron Johnson
On Wed, Jan 17, 2024 at 9:41 AM Troels Arvin wrote: > Hello, > > I would like to allow a co-worker to perform a backup of a database, such > that the backup is saved to the database server itself. One use case is > that (s)he would like an extra backup of a database, just before an > application

Re: Initiate backup from routine?

2024-01-17 Thread Pyrote
On Wednesday, January 17, 2024, Troels Arvin wrote: Is it possible to call pg_dump (or equivalent action) through a procedure/function? You could create a new schema and table that holds a flag column or a simple queue. Then setup a script/app on a 5 minute cron that checks the status of the

Re: pg_basebackup Restore problem

2024-01-17 Thread Ron Johnson
On Wed, Jan 17, 2024 at 11:11 AM Johnathan Tiamoh wrote: > Hello, > > I am trying to restore a pg_basebackup and have the following errors. > > You need to tell us the PG version number *and* show us the full command you ran. > nohup: ignoring input > tar: /tnt/backup/current/7400.tar.gz: Not

pg_basebackup Restore problem

2024-01-17 Thread Johnathan Tiamoh
Hello, I am trying to restore a pg_basebackup and have the following errors. nohup: ignoring input tar: /tnt/backup/current/7400.tar.gz: Not found in archive tar: /tnt/backup/current/7401.tar.gz: Not found in archive tar: /tnt/backup/current/7402.tar.gz: Not found in archive tar:

Re: Moving to Postgresql database

2024-01-17 Thread Tom Lane
Dominique Devienne writes: > On Tue, Jan 16, 2024 at 10:59 PM Tom Lane wrote: >> The problem is that now you have a switch somewhere (whether a GUC >> or something else, still a switch) that fundamentally changes the >> transactional semantics seen by applications. Run an application >> in the

Re: Initiate backup from routine?

2024-01-17 Thread Troels Arvin
Hello, David wrote: /  Are you able to install an untrusted language handler into the database?/ Yes, if need be. -- Regards, Troels Arvin

Re: Initiate backup from routine?

2024-01-17 Thread David G. Johnston
On Wednesday, January 17, 2024, Troels Arvin wrote: > > Is it possible to call pg_dump (or equivalent action) through a > procedure/function? > Are you able to install an untrusted language handler into the database? They are untrusted because they can basically get shell on the server. David

Initiate backup from routine?

2024-01-17 Thread Troels Arvin
Hello, I would like to allow a co-worker to perform a backup of a database, such that the backup is saved to the database server itself. One use case is that (s)he would like an extra backup of a database, just before an application update is deployed. The co-worker doesn't have shell access

Re: Moving to Postgresql database

2024-01-17 Thread Dominique Devienne
On Tue, Jan 16, 2024 at 10:59 PM Tom Lane wrote: > Dominique Devienne writes: > > But sure, I take your point, you can emulate statement-level (implicit) > > rollback via an explicit SAVEPOINT, and ROLLBACK to the savepoint > instead. > > > But my point remains, that something like what that

Re: Postgres Database Service Interruption

2024-01-17 Thread Laurenz Albe
On Tue, 2024-01-16 at 21:59 +0530, Bablu Kumar Nayak wrote: > I am writing to inform you that our PostgreSQL database service is currently > down. > We are experiencing an unexpected interruption, and we are seeking your > expertise > to help us resolve this issue promptly. > We would greatly