Tom Lane wrote:
> plus some not-very-large CPU-per-tuple charges
In my experience, cpu_tuple_cost should be higher. I've often had to
boost it to get good plans for a wide mix of queries in a load.
Doubling it to 0.02 is often not enough to get good plans. I've taken
it to 0.05 with production wo
niko.kiir...@mapvision.fi writes:
> I am working on a potentially large database table, let's call it
> "observation", that has a foreign key to table "measurement". Each
> measurement is associated with either none or around five observations. In
> this kind of situation, it is well known that the
On 10/23/2012 06:46 PM, niko.kiir...@mapvision.fi wrote:
> The following bug has been logged on the website:
>
> Bug reference: 7619
> Logged by: Niko Kiirala
> Email address: niko.kiir...@mapvision.fi
> PostgreSQL version: 9.2.1
> Operating system: Windows 7 SP 1 (64-bit)
> D
The following bug has been logged on the website:
Bug reference: 7619
Logged by: Niko Kiirala
Email address: niko.kiir...@mapvision.fi
PostgreSQL version: 9.2.1
Operating system: Windows 7 SP 1 (64-bit)
Description:
I am working on a potentially large database table,
