| From: | "Shridhar Daithankar" <shridhar_daithankar(at)persistent(dot)co(dot)in> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: concurrent writes |
| Date: | 2003-07-29 10:42:24 |
| Message-ID: | 3F269CE8.27725.52299C7@localhost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
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?
>More detailed: every process
> opens its own connection, starts a transaction, updates *different* rows
> and then commits. According to our postgres adminstrator, Postgres seems
> to behave differently on Linux and Solaris. Any ideas on that?
How it is different? It should be same, right?
Bye
Shridhar
--
QOTD: "I may not be able to walk, but I drive from the sitting posistion."
| From | Date | Subject | |
|---|---|---|---|
| Next Message | nolan | 2003-07-29 10:48:10 | Re: Can trigger procedures return value |
| Previous Message | Deepa K | 2003-07-29 10:40:12 | Can trigger procedures return value |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Jung | 2003-07-29 10:48:35 | Re: concurrent writes |
| Previous Message | Andreas Jung | 2003-07-29 10:33:06 | concurrent writes |