From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | Daniel Westermann <daniel(dot)westermann(at)dbi-services(dot)com> |
Cc: | Adam Brusselback <adambrusselback(at)gmail(dot)com>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
Subject: | Re: zheap: a new storage format for PostgreSQL |
Date: | 2018-11-19 11:01:08 |
Message-ID: | CAA4eK1L9VaCrdzttDbAXWXYtr8gKiqh24q+kvbNMW+=MB4w-Dw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Nov 19, 2018 at 3:59 PM Daniel Westermann
<daniel(dot)westermann(at)dbi-services(dot)com> wrote:
>
> > Thanks, it makes difference and keep us motivated for making progress.
> +1
>
> Is it intended behavior that a database can not be dropped when undo apply is running in the background?
>
Yes, we need to connect to the database for performing rollback
actions. Once the rollback for that database is over, undo apply
worker will exit and you should be able to drop the database.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | John Naylor | 2018-11-19 11:10:17 | Re: WIP: Avoid creation of the free space map for small tables |
Previous Message | Tomas Vondra | 2018-11-19 10:44:58 | Re: logical decoding vs. VACUUM FULL / CLUSTER on table with TOAST-ed data |