| From: | Jinyu <call_jinyu(at)126(dot)com> |
|---|---|
| To: | "Jim Nasby" <Jim(dot)Nasby(at)BlueTreble(dot)com> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Improve the concurency of vacuum full table and select statement on the same relation |
| Date: | 2015-10-13 15:18:32 |
| Message-ID: | 5c2bff8c.14872.15061c81122.Coremail.call_jinyu@126.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>it's approach to this is to summarily kill anything that attempts DDL on a table being repacked.
Why? I am confused with it. Could you please explain this?
Jinyu Zhang
thanks
At 2015-10-12 23:46:12, "Jim Nasby" <Jim(dot)Nasby(at)BlueTreble(dot)com> wrote:
>On 10/11/15 6:55 AM, Jinyu wrote:
>> Are there other solutions to improve the concurency of vacuum
>> full/cluster and select statement on the same relation?
>
>ISTM that if we were going to put effort into this it makes more sense
>to pull pg_repack into core. BTW, it's approach to this is to summarily
>kill anything that attempts DDL on a table being repacked.
>--
>Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
>Experts in Analytics, Data Architecture and PostgreSQL
>Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-10-13 15:27:52 | Re: Postgres service stops when I kill client backend on Windows |
| Previous Message | Tom Lane | 2015-10-13 15:15:01 | Re: bugs and bug tracking |