| From: | Marti Raudsepp <marti(at)juffo(dot)org> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andy Colson <andy(at)squeakycode(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: unlogged tables |
| Date: | 2010-12-08 14:52:33 |
| Message-ID: | AANLkTi=AKz8_w-z7zhSy9w4iOH4eW0iBQxJV6+0QTpiF@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
A very useful feature for unlogged tables would be the ability to
switch them back to normal tables -- this way you could do bulk
loading into an unlogged table and then turn it into a regular table
using just fsync(), bypassing all the WAL-logging overhead. It seems
this could even be implemented in pg_restore itself.
Which brings me to:
On Tue, Dec 7, 2010 at 20:44, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> 2. Any crash truncates the table, but a clean shutdown does not.
Seems that syncing on a clean shutdown could use the same
infrastructure as the above functionality.
Have you thought about switching unlogged tables back to logged? Are
there any significant obstacles?
Regards,
Marti
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitriy Igrishin | 2010-12-08 14:56:49 | Re: pg_type.typname of array types. |
| Previous Message | Dmitriy Igrishin | 2010-12-08 14:51:31 | Re: pg_type.typname of array types. |