Re: Why does the planner reduce the planned rows when filtering single values in an array

Thank you Tom, Every tool is a work in progress. Knowing it's just a fact of life for now is really helpful, I appreciate the response. From: Tom Lane Sent: Saturday, April 22, 2023 12:43 AM To: Isaiah Langford Cc: pgsql-general@lists.postgresql.org Subject: Re

Re: FW: Error!

On 4/22/23 07:31, Arquimedes Aguirre wrote: Hi Dear Good Morning! Please do not top post. Either bottom or inline post per: https://en.wikipedia.org/wiki/Posting_style How to know if I have connection or not connection? May you explain for more details? please. From the screenshot you

Re: How to verify postrgresql download on windows?

I am just trying to revive this question, I am still hoping to get an answer how can we verify the postgresql download on windows ? Thanks Ali On Wed, Feb 8, 2023 at 2:03 PM Ali M. wrote: > Hi the Postgresql binaries and installer are provided by EDB > How can i verify the download > > Usually

Re: How to verify postrgresql download on windows?

> On Wed, Feb 8, 2023 at 2:03 PM Ali M. wrote: > > > Hi the Postgresql binaries and installer are provided by EDB > > How can i verify the download > > > > Usually other projects provide a SHA256 hash list to verify the downloads > > EDB doesnt seem to provide that, so how else can i verify the d

SCROLLABLE/UPDATABLE cursor question

Hi All, I’m not sure where to ask the question so I’ll start here. Does anyone know if Postgres has any plans to support statements like FETCH/MOVE in the non-forward direction for SCROLLABLE/UPDATABLE cursors? -- Regards, Garfield A. Lewis

Re: SCROLLABLE/UPDATABLE cursor question

Garfield Lewis writes: > I’m not sure where to ask the question so I’ll start here. Does anyone know > if Postgres has any plans to support statements like FETCH/MOVE in the > non-forward direction for SCROLLABLE/UPDATABLE cursors? Doesn't that work already? regards, to

Why not use the calloc to replace malloc?

HI team, I'm a newbie to the postgres. When I learn the code of libpq, the achieve of PQmakeEmptyPGresult, cause my curiosity. The old version code: PQmakeEmptyPGresult(PGconn *conn, ExecStatusType status) {   PGresult *result;   result = (PGresult *) malloc(sizeof(PGresult));   

Re: Why not use the calloc to replace malloc?

Wen Yi writes: > [ use calloc to replace zeroing fields individually ] The reason we like to do it like that is that it provides greppability, that is you can search the source code to see where a particular field is initialized or modified. The backend code is often intentionally inefficient in