On Wed, Oct 31, 2012 at 11:39 AM, Merlin Moncure wrote:
> On Tue, Oct 30, 2012 at 4:58 PM, Jeff Janes wrote:
>> On Mon, Oct 29, 2012 at 5:11 PM, Catalin Iacob
>> wrote:
>>
>>> pgbouncer 1.4.2 installed from Ubuntu's packages on the same machine
>>> as Postgres. Django connects via TCP/IP to pgb
Josh Berkus writes:
>> Funny thing is, if I set constraint_exclusion=on, it works as
>> expected. But not with constraint_exclusion=partition.
> The difference between "on" and "partition" is how it treats UNION.
> This seems to be working as designed.
Well, what "partition" actually means is "o
> Funny thing is, if I set constraint_exclusion=on, it works as
> expected. But not with constraint_exclusion=partition.
The difference between "on" and "partition" is how it treats UNION.
This seems to be working as designed.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Se
Am 03.11.2012 16:20, schrieb Petr Praus:
Your CPUs are indeed pretty oldschool. FSB based, IIRC, not NUMA.
A process migration would be even more expensive there.
Ok, I've actually looked these up now... at the time these were current,
I was in the lucky situation to only deal with O
Am 02.11.2012 17:12, schrieb Petr Praus:
Your CPUs are indeed pretty oldschool. FSB based, IIRC, not NUMA. A
process migration would be even more expensive there.
Might be worth to
- manually pin (with taskset) the session you test this in to a
particular CPU (once on each socket)
