Re: [HACKERS] vacuum failure in current sources

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: prlw1(at)cam(dot)ac(dot)uk, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] vacuum failure in current sources
Date: 2000-01-21 03:53:39
Message-ID: 20000121125339J.t-ishii@sra.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk> writes:
> > This is with source from yesterday, but I seem to remember the same
> > happening to me on 6th January. It used to work before then. I don't
> > know where to look!
>
> > % psql template1
> > template1=> create database test;
> > CREATE DATABASE
> > template1=> \c test
> > You are now connected to database test.
> > test=> create table atable (x int);
> > CREATE
> > test=> insert into atable values (1);
> > INSERT 558537 1
> > test=> vacuum analyze atable;
> > NOTICE: Vacuum: table not found
> > VACUUM
> > test=> select version();
> > version
> > -------------------------------------------------------------------------
> > PostgreSQL 7.0.0 on i386-unknown-netbsd1.4p, compiled by gcc egcs-1.1.2
> > (1 row)
>
> Wow. It works fine for me. Platform-specific bug maybe? Can anyone
> else reproduce this?

I do not see the problem neither. This is RH 5.2.
--
Tatsuo Ishii

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Lockhart 2000-01-21 04:25:17 Re: [HACKERS] timezone problem?
Previous Message Bruce Momjian 2000-01-21 03:52:13 Re: [HACKERS] Re: Status on 7.0