Hi, Tom,
Tom Dunstan wrote:
>> On a unix box, when you're really crazy, and want to ignore all security
>> restrictions, you could even install pg_dump via inetd, and then
>> everyone connecting via TCP on the appropriate port gets a dump of the
>> database. :-)
>
> Oh, man, my head just explode
Tom Lane wrote:
> Andrew Dunstan <[EMAIL PROTECTED]> writes:
>
>> Then after you recover from your head exploding you start devising some
>> sort of sane API ...
>>
>
> That's the hard part. There is no percentage in having a library if
> it doesn't do anything significantly different fro
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Then after you recover from your head exploding you start devising some
> sort of sane API ...
That's the hard part. There is no percentage in having a library if
it doesn't do anything significantly different from what you could
accomplish via
Markus Schaber wrote:
Marlon Petry wrote:
But I would need to have installed pg_dump and pg_restore in machine
client?
Without having installed pg_dump and pg_restore,how I could make
pg_dump and pg_restore should be runnable (possible with a small shell /
bash wrapper script) without any "ins
Marlon Petry wrote:>>> > You can't. pg_dump in particular embodies an enormous amount of
> > knowledge that simply does not exist elsewhere. There is no> > dump/restore API, and there is nothing you can hook up to using JNI,> > AFAIK.> Recently, there was the proposal to extract
Marlon Petry wrote:>
> You can't. pg_dump in particular embodies an enormous amount of
> knowledge that simply does not exist elsewhere. There is no
> dump/restore API, and there is nothing you can hook up to using JNI,
> AFAIK.
Recently, there was the proposal to extract tha
> Marlon Petry wrote:
>> pg_dump and pg_restore do not need to run on the server machine.>> Why not>> just run them where you want the dump stored?>> But I would need to have installed pg_dump and pg_restore in machine
>> client?>> Without having installed pg_dump and pg_res
Hi, Marlon,
Marlon Petry wrote:
> But I would need to have installed pg_dump and pg_restore in machine
> client?
> Without having installed pg_dump and pg_restore,how I could make
pg_dump and pg_restore should be runnable (possible with a small shell /
bash wrapper script) without any "installat
Andrew Dunstan wrote:
> Marlon Petry wrote:
>>
>>
>> pg_dump and pg_restore do not need to run on the server machine.
>> Why not
>> just run them where you want the dump stored?
>>
>>
>>
>>
>> But I would need to have installed pg_dump and pg_restore in machine
>> client?
>> Without hav
Marlon Petry wrote:
pg_dump and pg_restore do not need to run on the server machine.
Why not
just run them where you want the dump stored?
But I would need to have installed pg_dump and pg_restore in machine
client?
Without having installed pg_dump and pg_restore,how I could m
>> The idea is to make one pg_dump of the server and to keep in the
> machine of client.> And to restore this pg_dump when it will be necessary through the> machine of the client.> Perhaps I will have that to use some store procedure in the server, I> do not know
>>pg_dump and pg_restore do not nee
Marlon Petry wrote:
The idea is to make one pg_dump of the server and to keep in the
machine of client.
And to restore this pg_dump when it will be necessary through the
machine of the client.
Perhaps I will have that to use some store procedure in the server, I
do not know
pg_dump and p
The idea is to make one pg_dump of the server and to keep in the
machine of client.And to restore this pg_dump when it will be necessary
through the machine of the client.Perhaps I will have that to use some store procedure in the server, I do not know
regardsMarlon2006/9/29, Albe Laurenz <
[EMAI
Marlon Petry wrote:
> I am trying to develop, a API to carry through backup and
> restore through JDBC.
> I think that the best form is to use JNI.
> Some Suggestion?
Do you mean 'backup' or 'export/dump'?
If you mean 'export', do you need anything besides SQL?
If you mean 'backup', how do you
>> No, 2nd. WAL reflects layout of tuples in data files, so I don't see
>> how pg_dump output could be used.
>> I'll really appreciate if someone will help with this issue ... after
>> alpha testing will start next week.
>
> Where is this code? How can we get it?
Code is in CVS.
Philip Warner al
On Thu, 12 Oct 2000, Mikheev, Vadim wrote:
> > > Could this be added? I am willing to help with the coding.
> >
> > This is what Version 7.1 WAL is all about.
> > There might be some help wanted in one of the possible backup methods:
> > 1. a pg_dumpall restore, and a subsequent restore of
> > Could this be added? I am willing to help with the coding.
>
> This is what Version 7.1 WAL is all about.
> There might be some help wanted in one of the possible backup methods:
> 1. a pg_dumpall restore, and a subsequent restore of logs
> 2. a restore of a "physical backup of d
Bruce Momjian wrote:
> Lamar Owen Wrote:
> > And we thought 7.0 had alot of new features relative to 6.5.
> I think the true feature-killer release was 6.5.
Well, this is true. I skipped the whole 6.4 series for a reason :-). I
just _knew_ 6.5 was going to be _it_... (in actuality, it's b
> On Sun, 08 Oct 2000, Bruce Momjian wrote:
> > This will be in 7.1 as WAL (write-ahead log).
>
> What does this exactly mean? Will this WAL be an equivalent of the logical
> log of Informix? Where will they be kept? In the database, as a file, or as
> either?
> Looks pretty good. All that is n
> "Martin A. Marques" wrote:
> >
> > On Sun, 08 Oct 2000, Bruce Momjian wrote:
> > > This will be in 7.1 as WAL (write-ahead log).
> >
> > What does this exactly mean? Will this WAL be an equivalent of the logical
> > log of Informix? Where will they be kept? In the database, as a file, or as
>
"Martin A. Marques" wrote:
>
> On Sun, 08 Oct 2000, Bruce Momjian wrote:
> > This will be in 7.1 as WAL (write-ahead log).
>
> What does this exactly mean? Will this WAL be an equivalent of the logical
> log of Informix? Where will they be kept? In the database, as a file, or as
> either?
> Look
On Sun, 08 Oct 2000, Bruce Momjian wrote:
> This will be in 7.1 as WAL (write-ahead log).
What does this exactly mean? Will this WAL be an equivalent of the logical
log of Informix? Where will they be kept? In the database, as a file, or as
either?
Looks pretty good. All that is needed after th
This will be in 7.1 as WAL (write-ahead log).
> On Mon, 02 Oct 2000, Hannu Krosing wrote:
> > "Martin A. Marques" wrote:
> > > Hi,
> > >
> > > I would like to know if postgres comes with some kind of backup
> > > application? I mean something that would do database backup and restore,
> > > somet
On Mon, 02 Oct 2000, Hannu Krosing wrote:
> "Martin A. Marques" wrote:
> > Hi,
> >
> > I would like to know if postgres comes with some kind of backup
> > application? I mean something that would do database backup and restore,
> > something like informix's ontape and logical logs.
>>
> Take a loo
"Martin A. Marques" wrote:
>
> Hi,
>
> I would like to know if postgres comes with some kind of backup application?
> I mean something that would do database backup and restore, something like
> informix's ontape and logical logs.
Take a look at pg_dump and pg_dumpall
-
Hannu
25 matches
Mail list logo
