Re: [BUGS] drop database doesn't work

2002-07-16 Thread Jerome Alet
On Tue, Jul 16, 2002 at 12:35:17PM -0400, Tom Lane wrote: > Jerome Alet <[EMAIL PROTECTED]> writes: > > if I drop a database and recreate a new one with the > > same name, the old datas and base schema are still there > > to annoy me. > > Looks to me like you created some stuff in template1. See

Re: [BUGS] Possible Bug? TEST CASE

2002-07-16 Thread Tom Lane
Francis Reader <[EMAIL PROTECTED]> writes: > To conclude, if you have many clients whose backends have infrequent write > accesses and then long periods of inactivity, but whose connection to the > database is left open, and other backends that are active which march on and > create new wal files,

Re: [BUGS] drop database doesn't work

2002-07-16 Thread Tom Lane
Jerome Alet <[EMAIL PROTECTED]> writes: > if I drop a database and recreate a new one with the > same name, the old datas and base schema are still there > to annoy me. Looks to me like you created some stuff in template1. See http://www.ca.postgresql.org/users-lounge/docs/7.2/postgres/managing

Re: [BUGS] Bug #712: Documentation Section 3.4 Binary Strings

2002-07-16 Thread Joe Conway
[EMAIL PROTECTED] wrote: > David Clark ([EMAIL PROTECTED]) reports a bug with a severity > Table 3-7 SQL Literal escaped octets shows the input escape > representation for a single quote as '\\'' , but the third paragraph > below table 3-8 SQL Output Escaped Octets says that the single quote

Re: [BUGS] Possible Bug? TEST CASE

2002-07-16 Thread Francis Reader
The following is a simple test case to demonstrate a backend not closing a file descriptor to wal file, under Linux 2.4.17 and PG 7.1.3 In session1: Using psql cmd, create a table. Perform an insert on that table. In session2: Issue psql run "ls -l /proc/*/fd/* | grep pg_xlog" This will list

[BUGS] drop database doesn't work

2002-07-16 Thread Jerome Alet
POSTGRESQL BUG REPORT TEMPLATE Your name : Jerome Alet Your email address : [EMAIL PROTECTED] Sys

Re: [BUGS] pgDataRead

2002-07-16 Thread Tom Lane
[EMAIL PROTECTED] writes: > Warning: PostgreSQL query failed: pqReadData() -- backend closed the channe= > l unexpectedly. This probably means the backend terminated abnormally befor= > e or while processing the request. Can you provide a stack backtrace from the crashed backend? There should be

[BUGS] Bug #713: pgreaddata

2002-07-16 Thread pgsql-bugs
Daniel Ch. ([EMAIL PROTECTED]) reports a bug with a severity of 2 The lower the number the more severe it is. Short Description pgreaddata Long Description Hallo everybody, At first my greetings to all. This is first time when I write a letter to this group, and to any group so please be patien

[BUGS] Bug #712: Documentation Section 3.4 Binary Strings

2002-07-16 Thread pgsql-bugs
David Clark ([EMAIL PROTECTED]) reports a bug with a severity of 4 The lower the number the more severe it is. Short Description Documentation Section 3.4 Binary Strings Long Description In the user guide, section 3.4 binary strings Table 3-7 SQL Literal escaped octets shows the input escape re

[BUGS] pgDataRead

2002-07-16 Thread ad966
Hallo everybody, At first my greetings to all. This is first time when I write a letter to this group, and to any group so please be patient for my mistakes.   I work with postgreSQL 7.1. Yesterday I made a migration to version 7.2.1. Everythings seemds to be OK but when in some queries I hav