On 2018-Dec-17, Tom Lane wrote:
> Queries like yours are kinda sorta counterexamples to that, but pretty
> much all the ones I've seen seem like crude hacks (and this one is not
> an exception). Writing a bunch of code to support them feels like
> solving the wrong problem. Admittedly, it's not
Wondering if anyone had any thoughts on how to tweak my setup to get it
to read many files at once instead of one at a time when using file fdw
and partitions. We have a bunch of data tied up in files (each file > 4M
rows, 5,000+ files per year) that I would like to be able to query
directly us
Hi All,
I am looking into a performance issue and needed your input and thoughts.
We have table (non-partitioned) of 500Gb with 11 indexes
+--+---+--+-+--+-++++
| row_estimate | total_bytes | inde
On Wed, 19 Dec 2018 at 19:04, anand086 wrote:
> We have noticed this increase in execution times for the sqls only when
> autovacuum runs and it runs with prevent wraparound mode. I think during the
> autovacuum process the Buffers: shared hit are increasing causing increase
> in execution time.
>
On Tue, Dec 18, 2018 at 08:39:36PM -0800, Patrick Mulrooney wrote:
> Wondering if anyone had any thoughts on how to tweak my setup to get it to
> read many files at once instead of one at a time when using file fdw and
> partitions.
I found this:
https://www.postgresql.org/docs/current/parallel-s
Justin,
Thanks for the idea. I pulled down the source for multicorn and added that to
it. I do not see parallel queries in the analyze output (unless I force it and
then it only gets one worker), but it does look like it is reading more than
one file at once if I go with a non-partitioned table
