| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kevin Brown <kevin(at)sysexperts(dot)com> |
| Cc: | Hackers <pgsql-hackers(at)postgresql(dot)org>, pgsql-performance(at)postgresql(dot)org, Advocacy <pgsql-advocacy(at)postgresql(dot)org> |
| Subject: | Re: [PERFORM] [HACKERS] More benchmarking of wal_buffers |
| Date: | 2003-02-14 04:14:49 |
| Message-ID: | 3914.1045196089@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers pgsql-performance |
Kevin Brown <kevin(at)sysexperts(dot)com> writes:
> What happens when the only transaction running emits more WAL log data
> than wal_buffers can handle? A flush happens when the WAL buffers
> fill up (that's what I'd expect)? Didn't find much in the
> documentation about it...
A write, not a flush (ie, we don't force an fsync). Also, I think it
writes only a few blocks, not all the available data. Don't recall the
details on that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2003-02-14 04:15:13 | Re: [HACKERS] Changing the default configuration |
| Previous Message | Josh Berkus | 2003-02-14 04:00:35 | Re: [HACKERS] Changing the default configuration |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2003-02-14 04:15:13 | Re: [HACKERS] Changing the default configuration |
| Previous Message | Josh Berkus | 2003-02-14 04:00:35 | Re: [HACKERS] Changing the default configuration |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-02-14 04:18:52 | Re: JBoss CMP Performance Problems with PostgreSQL 7.2.3 |
| Previous Message | Josh Berkus | 2003-02-14 04:00:35 | Re: [HACKERS] Changing the default configuration |