On Thu, 18 Oct 2001, Tom Lane wrote:
> Brian McCane <[EMAIL PROTECTED]> writes:
> > An interesting point was that the duplicated key was actually in the
> > table, but the existing unique index was happy as a clam.
>
> Hmm. What datatype is the key, and what PG version are you running?
>
> The o
Brian McCane <[EMAIL PROTECTED]> writes:
> An interesting point was that the duplicated key was actually in the
> table, but the existing unique index was happy as a clam.
Hmm. What datatype is the key, and what PG version are you running?
The only known cause of such problems at the moment is
On Sun, 14 Oct 2001, Marc Spitzer wrote:
> In article <[EMAIL PROTECTED]>, Brian McCane wrote:
> >
> > Being the perpetually lazy person that I am, I have written a PERL script
> > that takes care of indexes on a live system. You tell the script the
> > database and table to re-index. It then f
In article <[EMAIL PROTECTED]>, Brian McCane wrote:
>
> Being the perpetually lazy person that I am, I have written a PERL script
> that takes care of indexes on a live system. You tell the script the
> database and table to reindex. It then finds a list of indexes for the
> table and creates e
Sorry, I realize now that my original post was very
unclear. I read the FAQ and therefore know that just
running VACUUM will not show decreased disk usage.
However, I would expect that after deleting 1/6 of the
db and running vacuum, the db would quit growing on
the disk (except for maybe some log
On Sun, 7 Oct 2001, Marc Spitzer wrote:
> In article <[EMAIL PROTECTED]>,
> Joshua Franklin wrote:
> > I've got a large database that's getting too big. I
> > checked with the users and deleted approximately 1/6th
> > of the records (we have archived backups) and then ran
> > a VACUUM, which took
In article <[EMAIL PROTECTED]>,
Joshua Franklin wrote:
> I've got a large database that's getting too big. I
> checked with the users and deleted approximately 1/6th
> of the records (we have archived backups) and then ran
> a VACUUM, which took a really long time to complete
> (several days). Bu
I've got a large database that's getting too big. I
checked with the users and deleted approximately 1/6th
of the records (we have archived backups) and then ran
a VACUUM, which took a really long time to complete
(several days). But, the disk space usage doesn't seem
to have changed. Do I need to
