Re: How batch processing works

On 10/4/24 1:05 PM, Lok P wrote: On Mon, Sep 23, 2024 at 12:53 AM Peter J. Holzer > wrote: > Thank you so much. > I was expecting method-3(batch insert) to be the fastest or atleast as you said > perform with similar speed as method-2 (row by ro

Re: How batch processing works

On Mon, Sep 23, 2024 at 12:53 AM Peter J. Holzer wrote: > > > Thank you so much. > > I was expecting method-3(batch insert) to be the fastest or atleast as > you said > > perform with similar speed as method-2 (row by row insert with batch > commit) > > Oops, sorry! I wrote that the wrong way aro

Re: Question on session timeout

On 10/4/24 12:36, sud wrote: And yes it's RDS. The errors which we were seeing were related to the data bit not related to connections. The errors occur in a connection so they are related. -- Adrian Klaver adrian.kla...@aklaver.com

Re: Question on session timeout

On Tue, Oct 1, 2024 at 5:45 PM Greg Sabino Mullane wrote: > On Tue, Oct 1, 2024 at 1:57 AM sud wrote: > >> *Where are you getting the ~2000 count from?* >> Seeing this in the "performance insights" dashboard and also its matching >> when I query the count of sessions from pg_stat_activity. >> >

Re: Error Building Postgres 17.0 from Source

> On Oct 4, 2024, at 12:34, Tom Lane wrote: > > If so, the difference is that up to v16 we > included prebuilt HTML docs in the tarballs, but as of v17 we don't. > So "make world" now triggers a local docs build where before it > didn't. Ah! That would be it.

Re: Error Building Postgres 17.0 from Source

Christophe Pettus writes: > On Oct 4, 2024, at 12:05, Tom Lane wrote: >> Yeah, that's what it looks like. I'm a bit confused though because >> 16.x should have failed the same way: building our docs without local >> DTDs has failed for well over a year now [1]. > To add confusion to the fire,

Re: Error Building Postgres 17.0 from Source

> On Oct 4, 2024, at 12:05, Tom Lane wrote: > > Yeah, that's what it looks like. I'm a bit confused though because > 16.x should have failed the same way: building our docs without local > DTDs has failed for well over a year now [1]. To add confusion to the fire, I was successfully buildin

Re: Error Building Postgres 17.0 from Source

Christophe Pettus writes: > On Oct 4, 2024, at 09:35, Corbin Cavolt wrote: >> I'm having a problem building Postgres 17.0 from source. I'm able to build >> all the 16.x versions just fine; I'm running into an error specifically with >> version 17.0. > You might try installing the Debian packag

Re: Error Building Postgres 17.0 from Source

> On Oct 4, 2024, at 09:35, Corbin Cavolt wrote: > > Hi, > > I'm having a problem building Postgres 17.0 from source. I'm able to build > all the 16.x versions just fine; I'm running into an error specifically with > version 17.0. I use a devcontainer for development with my own postgres >

Error Building Postgres 17.0 from Source

Hi, I'm having a problem building Postgres 17.0 from source. I'm able to build all the 16.x versions just fine; I'm running into an error specifically with version 17.0. I use a devcontainer for development with my own postgres feature here: https://github.com/ccavolt/devcontainer-features/tree

Re: CLOSE_WAIT pileup and Application Timeout

On 10/3/24 21:29, KK CHN wrote: List, I am facing a  network (TCP IP connection closing issue) . Running a  mobile tablet application, Android application to update the status of vehicles fleet say around 1000 numbers installed with the app on each vehicle along  with a  vehicle tracking  app

Re: How to troubleshoot: ERROR: cache lookup failed for type?

On 10/4/24 05:09, Marcin Barczyński wrote: Hello! When reindexing a table, PostgreSQL returns the following errors for two of its indexes: Index foo_idx1 on foo failed with error: failed to find parent tuple for heap-only tuple at (1162372,1) in table "foo" Index foo_idx2 on foo failed with err

How to troubleshoot: ERROR: cache lookup failed for type?

Hello! When reindexing a table, PostgreSQL returns the following errors for two of its indexes: Index foo_idx1 on foo failed with error: failed to find parent tuple for heap-only tuple at (1162372,1) in table "foo" Index foo_idx2 on foo failed with error: failed to find parent tuple for heap-only

Re: CLOSE_WAIT pileup and Application Timeout

If I understand clearly, postgresql is used as a Data server for the backend, and so the Android app does not connect directly to postgresql. The first idea is a problem on closing or recycling the connection by the backend after executing the request. Maybe wrong client connection pooling settings