Re: BUG #6635: TRUNCATE didn't recreate init fork.

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: kurosawa-akira(at)mxc(dot)nes(dot)nec(dot)co(dot)jp
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6635: TRUNCATE didn't recreate init fork.
Date: 2012-05-11 13:50:05
Message-ID: CA+TgmobVqpRTjRBd62iu2=7FDFQ9N22Me9x1+RDoO7oTReEwiQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, May 10, 2012 at 1:32 AM, <kurosawa-akira(at)mxc(dot)nes(dot)nec(dot)co(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2012-05-11 13:52:57 Re: BUG #6629: Creating a gist index fails with "too many LWLocks taken"
Previous Message Heikki Linnakangas 2012-05-11 10:07:03 Re: BUG #6629: Creating a gist index fails with "too many LWLocks taken"