Re: [HACKERS] Avoiding tuple construction/deconstruction during joining

2005-03-20 Thread Miroslav Šulc
Tom Lane wrote: So I have some results. I have tested the query on both PostgreSQL 8.0.1 and MySQL 4.1.8 with LIMIT set to 30 and OFFSET set to 6000. PostgreSQL result is 11,667.916 ms, MySQL result is 448.4 ms. That's a fairly impressive discrepancy :-(, and even the slot_getattr() patch th

Re: [HACKERS] Avoiding tuple construction/deconstruction during joining

2005-03-20 Thread Miroslav Šulc
Tom Lane wrote: =?windows-1250?Q?Miroslav_=8Aulc?= <[EMAIL PROTECTED]> writes: seriously, I am far below this level of knowledge. But I can contribute a test that (maybe) can help. I have rewritten the query so it JOINs the varchar() fields (in fact all fields except the IDPK) at the last INNE

Re: [HACKERS] Avoiding tuple construction/deconstruction during joining

2005-03-14 Thread Tom Lane
=?windows-1250?Q?Miroslav_=8Aulc?= <[EMAIL PROTECTED]> writes: > seriously, I am far below this level of knowledge. But I can contribute > a test that (maybe) can help. I have rewritten the query so it JOINs the > varchar() fields (in fact all fields except the IDPK) at the last INNER > JOIN. Th

[HACKERS] Avoiding tuple construction/deconstruction during joining

2005-03-14 Thread Tom Lane
=?ISO-8859-2?Q?Miroslav_=A9ulc?= <[EMAIL PROTECTED]> writes: > [ concerning a deeply nested LEFT JOIN to get data from a star schema ] > So I have some results. I have tested the query on both PostgreSQL 8.0.1 > and MySQL 4.1.8 with LIMIT set to 30 and OFFSET set to 6000. PostgreSQL > result is