Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #6635: TRUNCATE didn't recreate init fork. - Mailing list pgsql-bugs

From Robert Haas
Subject Re: BUG #6635: TRUNCATE didn't recreate init fork.
Date
Msg-id CA+TgmobVqpRTjRBd62iu2=7FDFQ9N22Me9x1+RDoO7oTReEwiQ@mail.gmail.com
Whole thread Raw
In response to BUG #6635: TRUNCATE didn't recreate init fork.  (kurosawa-akira@mxc.nes.nec.co.jp)
List pgsql-bugs
Tree view 
On Thu, May 10, 2012 at 1:32 AM,  <kurosawa-akira@mxc.nes.nec.co.jp> wrote:
> When I executed TRUNCATE command to unlogged table,
> init fork of new relfilenode (include toast) wasn't created.

Fixed, thanks for the report!

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-bugs by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: BUG #6629: Creating a gist index fails with "too many LWLocks taken"
Next
From: Tom Lane
Date:
Subject: Re: BUG #6629: Creating a gist index fails with "too many LWLocks taken"