From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | prlw1(at)cam(dot)ac(dot)uk |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | vacuum failure in current sources |
Date: | 2000-01-21 01:58:03 |
Message-ID: | 26643.948419883@sss.pgh.pa.us |
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?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Xun Cheng | 2000-01-21 02:19:40 | Re. [HACKERS] Some notes on optimizer cost estimates |
Previous Message | Tatsuo Ishii | 2000-01-21 01:56:51 | Re: [HACKERS] timezone problem? |