| From: | Ivan Kartyshov <i(dot)kartyshov(at)postgrespro(dot)ru> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: WIP: long transactions on hot standby feedback replica / proof of concept |
| Date: | 2017-10-24 07:56:15 |
| Message-ID: | 9446d0d72ef33c64f542daaf6fafb48f@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello. I made some bugfixes and rewrite the patch.
Simon Riggs писал 2017-09-05 14:44:
> As Alexander says, simply skipping truncation if standby is busy isn't
> a great plan.
>
> If we defer an action on standby replay, when and who will we apply
> it? What happens if the standby is shutdown or crashes while an action
> is pending.
After crash standby server will go to the nearest checkout and will
replay
all his wal`s to reach consistent state and then open for read-only
load.
(all collected wal`s will be replayed in right way, I meant wal`s that
truncates table and wal`s that make table grow)
--
Ivan Kartyshov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
| Attachment | Content-Type | Size |
|---|---|---|
| standby_truncate_skip_v4.patch | text/x-diff | 8.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2017-10-24 09:10:53 | Re: Parallel Hash take II |
| Previous Message | amul sul | 2017-10-24 07:13:12 | Re: [POC] hash partitioning |