Question: Why Are File Descriptors Not Closed and Accounted for PostgreSQL Backends?

Hi PostgreSQL Community, when a backend process starts, pq_init is called where it opens a FD during  CreateWaitEventSet() if (!AcquireExternalFD()) { /* treat this as though epoll_create1 itself returned EMFILE */ elog(ERROR, "epoll_create1 failed: %m"); } set->epoll_fd = epoll_create1(EPOLL_CL

Re: Question: Why Are File Descriptors Not Closed and Accounted for PostgreSQL Backends?

innakangas wrote --- On 24/05/2024 15:17, Srinath Reddy Sadipiralla wrote: > Hi PostgreSQL Community, > when a backend process starts, pq_init is called where it opens a FD during  > CreateWaitEventSet() > > > if (!AcquireExternalFD()) > { > /* treat this as though epoll

Re: \watch 0 or \watch 0.00001 doesn't do what I want

s the query just once and then hangs forever, until I hit CTRL-C to cancel. hi heikki,but i am in pg 14.7 and the query is running perfectly without getting stuck. Regards, Srinath Reddy Sadipiralla Member Technical Staff ZOHO

[PATCH] immediately kill psql process if server is not running.

using select() and recv()  functions .If either one of the value is returned we terminate the psql process. 2) Doing the same thing as above but in single process using readline callbacks(only supports --with-readline) Regards, Srinath Reddy Sadipiralla Member Technical Staff Zoho 0001

Re: Building Postgres 17.0 with meson

gresql.org/docs/current/install-meson.html#CONFIGURE-EXTRA-LIB-DIRS-MESON Regards, Srinath Reddy Sadipiralla Member Technical Staff ZOHO

Re: Why we need to check for local buffers in BufferIsExclusiveLocked and BufferIsDirty?

Hi, added this bug to commitfest https://commitfest.postgresql.org/51/5428/  Regards, Srinath Reddy Sadipiralla Member of Technical Staff Zoho

Fwd: Re: Why we need to check for local buffers in BufferIsExclusiveLocked and BufferIsDirty?

Forwarded message From: Srinath Reddy Sadipiralla To: "Nazir Bilal Yavuz", "pgsql-hackers", "Andres Freund" Date: Mon, 09 Dec 2024 10:14:06 +0530 Subject: Re: Why we need to check for local buffers in BufferIsExclusiveLocked and BufferI

Re: Why we need to check for local buffers in BufferIsExclusiveLocked and BufferIsDirty?

On Sun, 08 Dec 2024 18:23:21 +0530 Nazir Bilal Yavuz wrote --- Hi Srinath, On Sat, 7 Dec 2024 at 11:17, Srinath Reddy Sadipiralla <mailto:srinath.re...@zohocorp.com> wrote: > > On Fri, 06 Dec 2024 16:40:51 +0530 Nazir Bilal Yavuz > > <mailto:byav

Why we need to check for local buffers in BufferIsExclusiveLocked and BufferIsDirty?

Hi, Why we need to check for local buffers in BufferIsExclusiveLocked and BufferIsDirty?,these 2 functions are called only from XlogRegisterBuffer,AFAIK which will be called only for permanent relations.Please correct me if i am wrong. Regards, Srinath Reddy Sadipiralla Member of Technical

Re: Why we need to check for local buffers in BufferIsExclusiveLocked and BufferIsDirty?

> On Thu, 05 Dec 2024 21:11:42 +0530 Andres Freund > <mailto:and...@anarazel.de> wrote --- > Hi, > On 2024-12-05 18:38:16 +0530, Srinath Reddy Sadipiralla wrote: >> Why we need to check for local buffers in BufferIsExclusiveLocked and >> BufferIsDirty

Re: Why we need to check for local buffers in BufferIsExclusiveLocked and BufferIsDirty?

s my patch to this looks good?🤔 Regards, Srinath Reddy Sadipiralla Member of Technical Staff Zoho

Re: Make wal_receiver_timeout configurable per subscription

terval. > > +1 for extending this idea for other GUCs as well. -- Thanks, Srinath Reddy Sadipiralla EDB: https://www.enterprisedb.com/

Re: Suggestion to add --continue-client-on-abort option to pgbench

lag, case ESTATUS_DEADLOCK_ERROR: stats->deadlock_failures++; break; + case ESTATUS_OTHER_SQL_ERROR: + stats->other_sql_failures++; + break; default: /* internal error which should never occur */ pg_fatal("unexpected error status: %d", estatus); -- Thanks, Srinath Reddy Sadipiralla EDB: https://www.enterprisedb.com/

Support for Physical Column Reordering in PG

ql command to reposition the column like other databases makes sense? thoughts ? -- Thanks, Srinath Reddy Sadipiralla EDB: https://www.enterprisedb.com/

Custom GUCs and typos

refix. 3) I also added all the above support for the SET command also which previously was not there. 4) TODO: add support for ALTER SYSTEM SET ,if this patch makes sense. thoughts? [0] https://www.postgresql.org/message-id/flat/196f3f8e12f.87666a6c16169.9160742057750715009%40zohocorp.com --

Re: [Util] Warn and Remove Invalid GUCs

On Thu, May 22, 2025 at 9:00 PM Tom Lane wrote: > Srinath Reddy Sadipiralla writes: > > the extension is loaded and then i entered the bogus extension GUC into > > postgresql.conf and restarted, i did not observe any complain/warning . > > Were you looking in the right p

Re: [Util] Warn and Remove Invalid GUCs

+ { + struct config_generic *var = hentry->gucvar; + + if((var->flags & GUC_CUSTOM_PLACEHOLDER) != 0 && !has_valid_class_prefix(var->name)){ + ereport(WARNING, + (errcode(ERRCODE_INVALID_NAME), + errmsg("invalid configuration parameter name \"%s\", removing it", + var