Search Postgresql Archives

Re: [Q] optmizing postgres for 'single client' / many small queries

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"V S P" <toreason@xxxxxxxxxxx> writes:
> The application typicall goes like this

> select id, child_tb_key_id, <fields with parms> from tb1

> then for each selected row above
>      select from the child table do a select (like the above)

> and so on -- many levels deep

Seems like you need to fix your data representation so that this
operation can be collapsed into one query.  The main problem looks
to be a bogus decision to have separate child tables rather than
one big table with an extra key column.

			regards, tom lane

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux