From: | Patric Bechtel <bechtel(at)ipcon(dot)de> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Query length restriction in v3 protocol? |
Date: | 2006-05-09 15:47:03 |
Message-ID: | 4460B977.9070005@ipcon.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I'm struggling with hibernate and postgresql, because after some
performance analysis, it seems that it's wise to use table per concrete
class mapping, which means that all polymorphic queries result in huge
(I mean, very huge) union queries.
The question that I have is, if there's any length restriction regarding
on commands sent to the backend. I've seen queries 1.5 MB long, is that
really a problem or is there another solution for that (could be that
it's only possible with views in between or such)?
Normally I wouldn't even dare to send such beasts to the backend because
I would worry about parsing times and such, but I've seen the
performance of outer join queries over 5-9 tables (=inheritance depth in
O/R model), which is even more scary...
Thanks in advance,
- --
Mit freundlichen Gruessen / Regards
Patric Bechtel, IPCON Informationssysteme OHG
Kontakt: http://www.ipcon.de/kontakt.php
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (MingW32)
Comment: GnuPT 2.5.2
iD8DBQFEYLl2fGgGu8y7ypARAktCAKDMOBCM/1DviG0xGJ+TWHM2By6ZSACgjPxC
GdcrQsQkZeO5+hO9yF0jdKU=
=cFRc
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Lewis | 2006-05-09 17:19:33 | Re: Query length restriction in v3 protocol? |
Previous Message | MAIGNAN Luc | 2006-05-09 15:36:07 | Newbie question |