Planner not choosing GIN index

A client had an issue with a where that had a where clause something like this: WHERE 123456 = ANY(integer_array_column) I was surprised that this didn't use the pre-existing GIN index on integer_array_column, whereas recoding as WHERE ARRAY[123456] <@ integer_array_column did cause the GIN i

Re: Shared_buffers

Here's one cook article on using pg_buffercache... https://www.keithf4.com/a-large-database-does-not-mean-large-shared_buffers/ Regards, Michael Vitale Justin Pryzby Tuesday, March 12, 2019 4:11 PM I've tuned ~40 postgres instances, primarily using log_checkpoint

Re: Shared_buffers

On Tue, Mar 12, 2019 at 04:03:11PM -0400, MichaelDBA wrote: > Set shared_buffers more accurately by using pg_buffercache extension and the > related queries during high load times. I've tuned ~40 postgres instances, primarily using log_checkpoints and pg_stat_bgwriter, with custom RRD graphs. pg_

Re: Shared_buffers

Set shared_buffers more accurately by using pg_buffercache extension and the related queries during high load times. Regards, Michael Vitale Michael Lewis Tuesday, March 12, 2019 3:23 PM On Tue, Mar 12, 2019 at 2:29 AM Laurenz Albe >

Re: Shared_buffers

On Tue, Mar 12, 2019 at 2:29 AM Laurenz Albe wrote: > Daulat Ram wrote: > > I want to know about the working and importance of shared_buffers in > Postgresql? > > is it similar to the oracle database buffer cache? > > Yes, exactly. > > The main difference is that PostgreSQL uses buffered I/O, wh

Re: Shared_buffers

Daulat Ram wrote: > I want to know about the working and importance of shared_buffers in > Postgresql? > is it similar to the oracle database buffer cache? Yes, exactly. The main difference is that PostgreSQL uses buffered I/O, while Oracle usually uses direct I/O. Usually you start with share

Re: ERROR: found xmin from before relfrozenxid

Hi All, Apparently the issue appeared again in the same database but on different table . In the last time dumping and restoring the table helped. However, I dont understand why another table hit the bug if it was fixed in 9.6.9 while my db version is 9.6.10. Any idea ? ‫בתאריך יום ב׳, 4 בפבר׳ 20