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

On 2009-09-02, V S P wrote: > Hi, > our application is using Postgres in a rather unusuall way. > It is used by a GUI application to store several hundred > thousand 'parameters'. Basically it is used like a big INI > file. > > There are about 50 tables with various parameters. > > The applicatio

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

Tom Lane writes: > Just out of curiosity, does anyone know of any ORM anywhere that doesn't > suck? They seem to be uniformly awful, at least in terms of their > interfaces to SQL databases. If there were some we could recommend, > maybe people would be less stuck with these bogus legacy archite

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

Hi, Tom Lane writes: > Just out of curiosity, does anyone know of any ORM anywhere that doesn't > suck? They seem to be uniformly awful, at least in terms of their > interfaces to SQL databases. If there were some we could recommend, > maybe people would be less stuck with these bogus legacy ar

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

On Thu, Sep 03, 2009 at 07:24:50AM -0700, Richard Broersma wrote: > On Wed, Sep 2, 2009 at 4:35 PM, David Fetter wrote: > > > Hibernate has the very nice feature of being able to get out of > > your way.  Properly used, it can keep completely out of the > > business of making (wrong) guesses based

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

On Wed, Sep 2, 2009 at 4:35 PM, David Fetter wrote: > Hibernate has the very nice feature of being able to get out of your > way.  Properly used, it can keep completely out of the business of > making (wrong) guesses based on DDL, which is what ORMs often do. > DBIx::Class

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

On Wed, Sep 02, 2009 at 02:45:39PM -0400, Tom Lane wrote: > "V S P" writes: > > Well, actually somebody has written a C++ ORM > > [ that is causing all your problems and you say you can't discard ] > > Just out of curiosity, does anyone know of any ORM anywhere that > doesn't suck? They seem to

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

I do not know of any for C++. That's why I started my own (which is not the one used for the problem I am having :- ) ) http://github.com/vladp/CppOrm it works with Pg 8.3+ and VC++ compiler sofar (but support for more platforms and Dbs will be added in the future). My Orm is not really an ORM be

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

"V S P" writes: > Well, actually > somebody has written a C++ ORM > [ that is causing all your problems and you say you can't discard ] Just out of curiosity, does anyone know of any ORM anywhere that doesn't suck? They seem to be uniformly awful, at least in terms of their interfaces to SQL da

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

Well, actually somebody has written a C++ ORM that allows to do things (just a sketch) class L: CDbCapable { public: int prop1; int prop2; } class A: CDbCapable { QArray list_of_props_xyz; } int main () { A inst1; inst1.create_or_update_DbSchemaIfNeeded(); inst1.read

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

"V S P" writes: > The application typicall goes like this > select id, child_tb_key_id, 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

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

Hi, yes, I am sure I have to continue supporting Postgres at this time, it would take enormous effor to change to something else But yes, sqlite or tokiocabinet in my view would be good options (the decison was made some time ago, unfortunately). On Wed, 02 Sep 2009 19:49 +0200, "Pavel Stehule"

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

Hello Are you sure, so you have to use PostgreSQL - maybe SQLite or memcached is better for your task. regards Pavel Stehule 2009/9/2 V S P : > Hi, > our application is using Postgres in a rather unusuall way. > It is used by a GUI application to store several hundred > thousand 'parameters'.  B

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

Hi, our application is using Postgres in a rather unusuall way. It is used by a GUI application to store several hundred thousand 'parameters'. Basically it is used like a big INI file. There are about 50 tables with various parameters. The application typicall goes like this select id, child_t