From: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: concurrent writes |
Date: | 2003-07-29 14:19:06 |
Message-ID: | 1059488346.7508.84.camel@haggis |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Tue, 2003-07-29 at 05:48, Andreas Jung wrote:
> On Tue, 2003-07-29 at 12:42, Shridhar Daithankar wrote:
> > On 29 Jul 2003 at 12:33, Andreas Jung wrote:
> > > we are running Postgres 7.3.3 successfully on our portal sites
> > > under Solaris. For a new project we have the requirement that
> > > N processes need to write update/insert within the same time and within
> > > the same transaction data in one table.
> >
> > What does it mean by same transaction data?
>
> should read "update/insert within the same time and within the same
> transaction in one table"
How can N number of transactions write into the database, all within
the *same* transaction?
--
+-----------------------------------------------------------------+
| Ron Johnson, Jr. Home: ron(dot)l(dot)johnson(at)cox(dot)net |
| Jefferson, LA USA |
| |
| "I'm not a vegetarian because I love animals, I'm a vegetarian |
| because I hate vegetables!" |
| unknown |
+-----------------------------------------------------------------+
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-07-29 14:22:44 | Re: pg_dumpall: query failed: |
Previous Message | Franco Bruno Borghesi | 2003-07-29 14:10:39 | Re: Batch processing |
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2003-07-29 14:25:37 | Re: an aggregate array function |
Previous Message | Carlos Guzman Alvarez | 2003-07-29 14:04:16 | Re: Passing server_encoding to the client is not future-proof |