Re: Creating table with data from a join

From: Marc Mamin <M(dot)Mamin(at)intershop(dot)de>
To: "'Igor Stassiy'" <istassiy(at)gmail(dot)com>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Creating table with data from a join
Date: 2015-07-15 12:58:39
Message-ID: B6F6FD62F2624C4C9916AC0175D56D8828C0423B@jenmbs01.ad.intershop.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> Marc, I am using postgres 9.4. I didn't benchmark, but intuitively the modulo operator will force traversing every record in table "a" 4 times, as it can't use an index.

Not necessarily. seq scans can be synchronized:

"This allows sequential scans of large tables to synchronize with each other, so that concurrent scans read the same block at about the same time and hence share the I/O workload. When this is enabled, a scan might start in the middle of the table and then "wrap around" the end to cover all rows, so as to synchronize with the activity of scans already in progress. This can result in unpredictable changes in the row ordering returned by queries that have no ORDER BY clause."

Marc

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ryan King - NOAA Affiliate 2015-07-15 14:13:53 Re: could not create shared memory segment: Invalid argument
Previous Message Adrian Klaver 2015-07-15 12:55:51 Re: unexpected data beyond EOF in block 260 of relation pg_tblspc