RE: Bash function from psql (v14)

2024-11-10 Thread Murthy Nunna
Thanks, Greg. 1. This means what I am trying to do is not meant to work. This won’t work even if I declare the function before calling it in PSQL. I get it. 2. You are correct. Function must be declared before the call. Thanks again.

Bash function from psql (v14)

2024-11-09 Thread Murthy Nunna
Hi, I am trying to code bash function and call it from psql. But it is failing. How can I get this to work. Creating a separate script instead of a function works, but I do not want to do that. I have too many variables to be passed back and forth. Any ideas? #!/bin/bash psql -d postgres -p 5

RE: psql help

2024-07-05 Thread Murthy Nunna
-Original Message- From: dep...@depesz.com Sent: Friday, July 5, 2024 6:05 AM To: Murthy Nunna Cc: pgsql-general@lists.postgresql.org Subject: Re: psql help [EXTERNAL] – This message is from an external sender On Fri, Jul 05, 2024 at 03:54:56AM +, Murthy Nunna wrote: > So

RE: psql help

2024-07-04 Thread Murthy Nunna
n Sent: Thursday, July 4, 2024 8:17 PM To: Murthy Nunna Cc: pgsql-general@lists.postgresql.org Subject: Re: psql help [EXTERNAL] – This message is from an external sender On Thu, Jul 4, 2024 at 4:56 PM Murthy Nunna mailto:mnu...@fnal.gov>> wrote: How can I rewrite the above in psql

psql help

2024-07-04 Thread Murthy Nunna
Hello: Following works- SELECT pid, pg_terminate_backend(pid) FROM pg_stat_activity WHERE pid IN (select unnest(pg_blocking_pids(pid)) from pg_stat_activity where cardinality(pg_blocking_pids(pid)) > 0) and usename = 'DBUSER_10' and now() - state_change

RE: pg_upgrade 10.2

2018-06-12 Thread Murthy Nunna
ry Sievers [mailto:gsiever...@comcast.net] Sent: Tuesday, June 12, 2018 6:24 PM To: Murthy Nunna Cc: Adrian Klaver ; pgsql-general@lists.postgresql.org; pgsql-ad...@lists.postgresql.org; pgsql-performa...@lists.postgresql.org Subject: Re: pg_upgrade 10.2 Murthy Nunna writes: > Hi Adrian, > &g

RE: pg_upgrade 10.2

2018-06-12 Thread Murthy Nunna
al Message- From: Adrian Klaver [mailto:adrian.kla...@aklaver.com] Sent: Tuesday, June 12, 2018 4:35 PM To: Murthy Nunna ; pgsql-general@lists.postgresql.org; pgsql-ad...@lists.postgresql.org; pgsql-performa...@lists.postgresql.org Subject: Re: pg_upgrade 10.2 On 06/12/2018 02:18 PM, Murthy N

RE: pg_upgrade 10.2

2018-06-12 Thread Murthy Nunna
[mailto:adrian.kla...@aklaver.com] Sent: Tuesday, June 12, 2018 4:13 PM To: Murthy Nunna ; pgsql-general@lists.postgresql.org; pgsql-ad...@lists.postgresql.org; pgsql-performa...@lists.postgresql.org Subject: Re: pg_upgrade 10.2 On 06/12/2018 01:58 PM, Murthy Nunna wrote: > Thanks Adrian.

RE: pg_upgrade 10.2

2018-06-12 Thread Murthy Nunna
e 12, 2018 3:48 PM To: Murthy Nunna ; pgsql-general@lists.postgresql.org; pgsql-ad...@lists.postgresql.org; pgsql-performa...@lists.postgresql.org Subject: Re: pg_upgrade 10.2 On 06/12/2018 01:34 PM, Murthy Nunna wrote: > In older versions of pg_upgrade (e.g from 9.2 to 9.3), I was able to >

pg_upgrade 10.2

2018-06-12 Thread Murthy Nunna
In older versions of pg_upgrade (e.g from 9.2 to 9.3), I was able to run pg_upgrade without stopping old cluster using the check flag. pg_upgrade -b -B -d -D -p 5432 -P 5434 -r -v -k -c Note the "c" flag at the end However pg_upgrade in 10 (I tried from 9.3 to 10.4), when I did not stop th