| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Greg Sabino Mullane <greg(at)endpoint(dot)com> |
| Cc: | pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: Unlogged tables cannot be truncated twice |
| Date: | 2011-05-30 21:18:20 |
| Message-ID: | 1306790274-sup-6596@alvh.no-ip.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Excerpts from Greg Sabino Mullane's message of lun may 30 12:00:43 -0400 2011:
> Wow, this one took a bit to narrow down. Here's the failing case:
>
> # create unlogged table foo (a text);
> CREATE TABLE
> # begin;
> BEGIN
> #* truncate table foo;
> TRUNCATE TABLE
> #* truncate table foo;
> ERROR: could not create file "base/19131/19183_init": File exists
>
> Very reproducible. The column types matter: if the only column
> is an INT, for example, the problem does not occur.
So 19183 is the toast table OID?
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2011-05-30 23:28:37 | Re: Unlogged tables cannot be truncated twice |
| Previous Message | Greg Sabino Mullane | 2011-05-30 20:53:09 | Re: Failed pgbench: setrandom invalid maximum number 0 |