From: Ian Cass <ian.cass@mBlox.com>
To: Gunther Schadow <gunther@aurora.regenstrief.org>
Cc: pgsql-sql@postgresql.org
Subject: Re: select failure
Date: Sun, 9 Jun 2002 21:13:46 +0100
Message-ID: <001701c20ff2$29e60d40$1af11f3e@xenon> (raw)
References: <083e01c20e29$7c99fdf0$6602a8c0@salamander>
<3D039A2C.5000906@aurora.regenstrief.org>
<001501c20fe7$a92436a0$1af11f3e@xenon>
<3D03B426.6070900@aurora.regenstrief.org>
> Rebuilding 27million rows shouldn't take 2 or 3 days. Are you
> sure you do a COPY ... FROM instead of individual INSERTs?
I need to refeed the data from application log files. They may or may not
have duplicate rows. The only way I can filter these it to feed them all in
parallel using Perl & DBI into a unique index. That's what takes the time.
Do you suggest I rebuild the entire database or just the affected table? I
have approx 400million rows in the entire database.
--
Ian Cass
>Also
> you may consider turning off indexes and deferring foreign key
> triggers. However, I don't need to do this to load a similar
> sized database overnight. YMMV, depends on machine speed too,
> of course.
>
> Good luck, and beware, I'm not really the pgsql geek who really
> understands your error. I just use common sense, so, don't take
> my word for gold w/r/t the recommendation to backtrack version and
> rebuild.
>
> regards,
> -Gunther
>
>
> >
> > --
> > Ian Cass
> >
> > ----- Original Message -----
> > From: "Gunther Schadow" <gunther@aurora.regenstrief.org>
> > To: "Ian Cass" <ian.cass@mblox.com>
> > Cc: <pgsql-sql@postgresql.org>
> > Sent: Sunday, June 09, 2002 7:10 PM
> > Subject: Re: [SQL] select failure
> >
> >
> >
> >>Ian Cass wrote:
> >>
> >>
> >>>Ideas where I should look for the answer to this problem & how I should
> >>>
> > fix
> >
> >>>it?
> >>>
> >>>observer=# select host, current_route, count(current_route)
> >>>observer-# from messages_200205
> >>>observer-# group by host, current_route;
> >>>FATAL 2: open of /var/lib/postgres/data/pg_clog/0534 failed: No such
> >>>
> > file
> >
> >>>or directory
> >>>
> >>
> >>OUCH! that looks quite bad. It's a postgresql internal error.
> >>What version of PostgreSQL do you run? Is this some beta version?
> >>Or do you have someone deleting files randomly?
> >>
> >>regards,
> >>-Gunther
> >>
> >>
> >>
> >>--
> >>Gunther Schadow, M.D., Ph.D. gschadow@regenstrief.org
> >>Medical Information Scientist Regenstrief Institute for Health Care
> >>Adjunct Assistant Professor Indiana University School of Medicine
> >>tel:1(317)630-7960 http://aurora.regenstrief.org
> >>
> >>
> >>
> >>---------------------------(end of broadcast)---------------------------
> >>TIP 2: you can get off all lists at once with the unregister command
> >> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
> >>
> >>
>
>
> --
> Gunther Schadow, M.D., Ph.D. gschadow@regenstrief.org
> Medical Information Scientist Regenstrief Institute for Health Care
> Adjunct Assistant Professor Indiana University School of Medicine
> tel:1(317)630-7960 http://aurora.regenstrief.org
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: ian.cass@mBlox.com, gunther@aurora.regenstrief.org
Subject: Re: select failure
In-Reply-To: <001701c20ff2$29e60d40$1af11f3e@xenon>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox