ion of the operating
system or resources available to the database server itself. Regardless, if
you have better suggestions please serve them up. :-)
-- Ben Scherrey
On Tue, Jun 25, 2019 at 11:01 PM Justin Pryzby wrote:
> On Tue, Jun 25, 2019 at 10:55:22PM +0700, Benjamin Scherrey wrote:
>
Have you done a VACUUM ANALYZE FULL on your database? This needs to be done
periodically to inform the server of the statistics of how the data and
relations are distributed across the database. Without this bad assumptions
by the planner can cause degradation of performance. Also, if you are using
What's the on disk cache size for each drive? The better HDD performance
problem won't be sustained with large amounts of data and several different
queries.
- - Ben Scherrey
On Tue, Jul 17, 2018, 12:01 PM Neto pr wrote:
> Dear,
> Some of you can help me understand this.
>
> This query plan i
You don't mention the size of your database. Does it fit in memory? If so
your disks aren't going to matter a whole lot outside of potentially being
i/o bound on the writes. Otherwise getting your data into SSDs absolutely
can have a few multiples of performance impact. The NVME M.2 drives can
real
