Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> wrote:
> Past discussion here suggests that the backends are strictly single
> threaded. While you might be able to use multiple threads - I don't know
> - I expect you'd need to protect all SPI access by a lock that
> serialized everything anyway.
> Doing it externally with a script / program that uses multiple
> connections might just be the way. Unfortunately that means that you
> don't get a single consistent snapshot - each connection will have its
> own, potentially different, view of the database state.
> A possible use for read only transactions being able to share a snapshot
> came up in discussion a few weeks ago. I guess this is another one.
> Craig Ringer
I fill tables with observation data, so the tables don't change except the
one for current day. So I don't need to care about different states
From what has been posted I think that C function can do the work for me.
But I would still appreciate some peace of code from which I can figure
out how this can be done, because I'm new to database programing.
In response to
pgsql-general by date
|Next:||From: Ross Boylan||Date: 2008-03-30 18:54:38|
|Subject: Re: database 1.2G, pg_dump 73M?!|
|Previous:||From: Naz Gassiep||Date: 2008-03-30 18:37:26|
|Subject: Re: Locale / Encoding mismatch|