Tena,
We have been very happy with star. It is a very nice pax,
cpio, gnutar,... replacement. You may want to give it a try.
Ken
On Tue, Aug 21, 2007 at 06:53:53PM -0700, Tena Sakai wrote:
> Hi Kevin,
>
> Yes, I have, but I am much more familiar with tar.
> I think I will go with the latest gnu
Thanks, Ken.
I just glanced at man page for star. It looks promising
and I will experiment with it. This may be the ticket.
Regards,
Tena
[EMAIL PROTECTED]
-Original Message-
From: Kenneth Marshall [mailto:[EMAIL PROTECTED]
Sent: Wed 8/22/2007 5:30 AM
To: Tena Sakai
Cc: Kevin Grittne
On Monday 20 August 2007 14:33, Juliann Meyer wrote:
> Currently running v7.4.8 postgres on a RHE Linux 4.0 box. Will be
> upgraded to postgres 8.2.x sometime this fall.
>
> Several of the tables in the database that resides on this system have
> lots of inserts and updates. Very little is delet
I'm looking for advice on how to best switch from warm standby processing to
"stand-in" production use in our (rather unusual) environment.
THE ENVIRONMENT
We have 72 counties spread around the state, each with their own database,
which contains the official data for that county's court system.
Hi,
I have a question about PgSQL. I am working at some project and I want
to have few tables with special properties:
There would be many rows and these would be changed every day for many
times. I want to be able to get know how did the row looked in given
time (f.e. 2 day ago, 6 minutes ago, 2
Hi List;
I want to determine which table is being vacuumed.
I ran this:
postgres=# select procpid, current_query from pg_stat_activity where
current_query = 'VACUUM';
procpid | current_query
-+---
9902 | VACUUM
(1 row)
Then I ran this:
postgres=# select relation fr
On 8/22/07, Kevin Grittner <[EMAIL PROTECTED]> wrote:
> THE QUESTION
>
> How do we create the PostgreSQL instance on the stand-in box?
>
> I see four possibilities:
>
> (1) Restore the latest base backup and apply all WAL files available.
> This is likely to be the slowest option.
I'm leaning to
Hi Everybody,
I had a bit of time to experiment with tar and star today
and I am no longer sure what the real issue is. Perhaps
some of you can clarify. Here's the test I ran:
There are many a ways to get the same thing done, but I
did it in a most intuitive way (to me). I had 3 windows
to the
Kevin Kempter <[EMAIL PROTECTED]> writes:
> Then I ran this:
> postgres=# select relation from pg_locks where pid = 9902;
> relation
> ---
> 82097999
> 143763216
> 143763215
> 143763193
> 143763193
> 143763217
> (7 rows)
> However none of these seem to have a corresponding pg_clas
Tena Sakai wrote:
> Hi Everybody,
>
> I had a bit of time to experiment with tar and star today
> and I am no longer sure what the real issue is. Perhaps
> some of you can clarify. Here's the test I ran:
>
> There are many a ways to get the same thing done, but I
> did it in a most intuitive wa
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tena Sakai wrote:
>> I had a bit of time to experiment with tar and star today
>> and I am no longer sure what the real issue is. Perhaps
>> some of you can clarify. Here's the test I ran:
> I don't think 'touch' is enough for tar to see the file as ch
Hi Tom,
Hi Bruce,
Thanks for your input. Fair enough. I redid it.
This time, in the first window, I ran this mini
shell program continuously:
while true
> do
> date >> big.input
> done
In the 2nd window:
tar cf ../moo.tar . > tar_errlog 2>&1
Tar returned the exit code 0. In the
12 matches
Mail list logo
