Skip site navigation (1) Skip section navigation (2)

Re: [PORTS] Port Bug Report: "drop database DBNAME;" command has critical bug!!!

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>
Cc: KiBaek Jeong <hannoory(at)chollian(dot)net>, pgsql-ports(at)postgreSQL(dot)org
Subject: Re: [PORTS] Port Bug Report: "drop database DBNAME;" command has critical bug!!!
Date: 1999-05-27 14:55:04
Message-ID: 199905271455.KAA00103@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-ports
> > Summary: "drop database DBNAME;" command has critical bug!!!
> 
> Seems to not be a problem in the current sources:
> 
> hahaha=> \c postgres
> connecting to new database: postgres
> postgres=> drop database hahaha;
> DESTROYDB
> postgres=> create database hahaha;
> CREATEDB
> postgres=> \c hahaha
> connecting to new database: hahaha
> hahaha=> \d
> Couldn't find any tables, sequences or indices!

6.4 did not flush buffers on database close, so this may have been the
source of the problem.  6.5 is OK.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist(at)candle(dot)pha(dot)pa(dot)us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to

pgsql-ports by date

Next:From: Unprivileged userDate: 1999-05-27 18:39:32
Subject: Port Bug Report: initdb, postmaster, db_id looking for file: libcurses.so.4
Previous:From: Thomas LockhartDate: 1999-05-27 13:31:40
Subject: Re: [PORTS] Port Bug Report: "drop database DBNAME;" command has critical bug!!!

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group