Re: max_wal_senders must die
| От | Josh Berkus |
|---|---|
| Тема | Re: max_wal_senders must die |
| Дата | |
| Msg-id | 4CBF6A7B.9060103@agliodbs.com обсуждение исходный текст |
| Ответ на | Re: max_wal_senders must die (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: max_wal_senders must die
Re: max_wal_senders must die |
| Список | pgsql-hackers |
> Quite. Josh, have you got any evidence showing that the penalty is
> only 10%? There are cases, such as COPY and ALTER TABLE, where
> you'd be looking at 2X or worse penalties, because of the existing
> optimizations that avoid writing WAL at all for operations where a
> single final fsync can serve the purpose. I'm not sure what the
> penalty for "typical" workloads is, partly because I'm not sure what
> should be considered a "typical" workload for this purpose.
If we could agree on some workloads, I could run some benchmarks. I'm
not sure what those would be though, given that COPY and ALTER TABLE
aren't generally included in most benchmarks. I could see how
everything else is effected, though.
-- -- Josh Berkus PostgreSQL Experts Inc.
http://www.pgexperts.com
В списке pgsql-hackers по дате отправления: