Joseph McClintock <[EMAIL PROTECTED]> writes:
> Now our database has grown and the pg_dump give me a 2.1 GB file which
> is taking 12 hours or more to restore, Yickes! I've tried compressing
> the dump file:
Compressing the dump file will make the restore slower, most likely,
because of the extra
On Tue, Dec 19, 2006 at 08:59:26 -0800,
Rickard Sjöström <[EMAIL PROTECTED]> wrote:
>
> If I decide to continue with 7.4 I guess the procedure to move the DATADIR to
> the new machine and then start the postgresql server there with the old
> DATADIR should work without problems?
The new machi
On Wed, 2006-12-20 at 10:37 +0100, Olivier Boissard wrote:
> Chris Hoover a écrit :
> > One other option is to shut the database down competely, and then do a
> > copy of the file system the new server. I have done this when I need
> > to move a very large database to a new server. I can copy 5
I have inherited the on going management of our company's PostgreSQL 8.0
database. I'm having a very serious problem with the restore process.
I've been running periodic pg_dumps from our production database and
then restoring the data on our development system. That has been working
find until now
Hi,
12h is a lot. i use the copy statement with binary option. this is
faster and takes less space.
try pg_dump with schema only and export your 2 tables with 2 single
statements. in that way i can
export my db in less than 3min without downtime (pg_dump produces a 9gb
file, binary dump 4.4gb)
Chris Hoover a écrit :
One other option is to shut the database down competely, and then do a
copy of the file system the new server. I have done this when I need
to move a very large database to a new server. I can copy 500GB's in
a couple of hours, where restoring my large databases backups
Hi
I just encountered a reproducable bug with plpgsql function "return
next" after drop column:
create table test (
id int not null primary key
);
insert into test values (1);
create or replace function get_test(int)
returns setof test
as 'declare
rec record;
begin
for r
Hi!
I'm tying to compile postgresql 8.2.0 under:
SunOS 5.8 Generic_117350-36 sun4u sparc SUNW,Sun-Blade-100
and got problems while compiling, the problem seems to be that gcc (or
configure) adds my username (sjostric) to the gcc command line. Like this:
gcc -O2 -Wall -Wmissing-prototypes -Wpoint
