Re: [Q] optmizing postgres for 'single client' / many small queries - Mailing list pgsql-general

From Tom Lane
Subject Re: [Q] optmizing postgres for 'single client' / many small queries
Date
Msg-id 14643.1251915961@sss.pgh.pa.us
Whole thread Raw
In response to [Q] optmizing postgres for 'single client' / many small queries  ("V S P" <toreason@fastmail.fm>)
Responses Re: [Q] optmizing postgres for 'single client' / many small queries
List pgsql-general
"V S P" <toreason@fastmail.fm> 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

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: PL/SQL & unset custom variable
Next
From: "V S P"
Date:
Subject: Re: [Q] optmizing postgres for 'single client' / many small queries