From: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
---|---|
To: | pgsql general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Practical maximums (was Re: PostgreSQL theoretical |
Date: | 2006-08-07 21:53:47 |
Message-ID: | 44D7B66B.6090505@cox.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Alvaro Herrera wrote:
> Ron Johnson wrote:
>
>> This is where a multi-threaded pg_tapedump would be more effective,
>> since it would be able to, for example, have 4 threads reading
>> (different parts of) the database and writing to 4 separate tape drives.
>
> It will be difficult to have a consistent dump though. You can't do
> that with separate transactions. (And you can't have multiple
> simultaneous readers without separate transactions.)
Absolutely, you're right. All "threads" must run from within the
same read-only transaction.
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "common sense" to white-power racists that
whites are superior to blacks, and that those with brown skins
are mud people.
However, that "common sense" is obviously wrong.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFE17ZrS9HxQb37XmcRAitSAKCo1/HaJ8ZsoGYFgGo2sHezWmqqWACbB9Mr
Hw4Xaalah+ZqExMwr4vu058=
=e33c
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Johnson | 2006-08-07 21:57:36 | Re: Practical maximums (was Re: PostgreSQL theoretical |
Previous Message | Ron Johnson | 2006-08-07 21:51:13 | Re: Practical maximums (was Re: PostgreSQL theoretical |