Re: New Zealand Postgis DBA job vacancy - Mailing list pgsql-general

From Martin Gainty
Subject Re: New Zealand Postgis DBA job vacancy
Date
Msg-id BLU172-W46D07E406E970F8459CE87AE380@phx.gbl
Whole thread Raw
In response to Re: New Zealand Postgis DBA job vacancy  (Bexley Hall <bexley401@yahoo.com>)
Responses Re: New Zealand Postgis DBA job vacancy
List pgsql-general
> From: bexley401@yahoo.com
> To: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] New Zealand Postgis DBA job vacancy
> >
> Thinking (entirely) *in* metric doesn't. The problem is working
> with *both*, simultaneously, requires some mental agility.
>
> Nearby, we have one of the few (only?) stretches of roadway that
> is marked in metric units (actually, I haven't driven it in a while
> and vaguely recall something about RE-marking it in "conventional"
> units). To most folks, it is a disturbing experience as they aren't
> accustomed to thinking in these. ("No, that's not 100MPH but
> 100kmph... big difference!")
MG>Posted Speed limit in the mahority of limited access highways in SouthAmerica is 100
MG>unless of course ...you're in a hurry
>
>
> > so...why doesn't Postgres port to embedded systems?
>
> IME, it requires lots of resources (the vast majority of embedded
> systems are resource starved -- resources == $$ and when you are
> selling things in volume, every penny saved adds up quickly!).
> Lots of MIPS, lots of RAM -- even the code footprint is "significant".
>
> OTOH, (again, IME) designing with the "relational table" construct
> makes coding a very different experience! Already being biased
> in favor of table-driven algorithms, I took this opportunity to
> move all the "const" tables out of my executables and into the
> DBMS (which takes a performance hit but keeps the code much more
> mutable). I've gone so far as to hide the filesystem from the
> applications -- objects that would have typically resided in
> ad hoc files are now stored in structured tables (eliminates
> the need to write lots of special parsers to be able to impose
> structure on what would otherwise be unstructured "bytes")
>
MG>so do you reduce CPU or IO when you take a java variable final int foo=1; and insert foo as a const column in a table?
MG>BTW Spring IOC has addressed this issue with lazy-init="true" (dont initialise the variable until referenced at runtime)
>
> --don
MG>Martin
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general

pgsql-general by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Cursor fetch Problem.
Next
From: Kirk Wythers
Date:
Subject: update table from a csv file