| From: | Tadipathri Raghu <traghu(dot)dba(at)gmail(dot)com> |
|---|---|
| To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | Pierre C <lists(at)peufeu(dot)com>, Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Why Wal_buffer is 64KB |
| Date: | 2010-03-29 07:05:50 |
| Message-ID: | 645d9d71003290005q2ba3b33fhca45d9e2f6067f3b@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Hi Scott,
Yes, May i know any particular reason for behaving this. Are its looking for
any consistency. I havnt got any clear picture here.
Could you Please explain this..
Thanks & Regards
Raghavendra
On Mon, Mar 29, 2010 at 12:15 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>wrote:
> On Mon, Mar 29, 2010 at 12:00 AM, Tadipathri Raghu <traghu(dot)dba(at)gmail(dot)com>
> wrote:
> > Hi All,
> >
> > Thank you for all the support.
> >
> > I have noticed one more thing here, that if you turn off the fsync and
> try
> > to run the transaction than its breaking the currnet filenode and
> generating
> > another filenode. Is it true that whenever you turn off or on the fsync
> the
> > filenode will break and create one more on that table.
>
> From what I understand, with fsync on or off the same stuff gets
> written. It's just not guaranteed to go out in the right order or
> right now, but eventually.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthew Wakeling | 2010-03-29 11:17:50 | Re: Optimizer showing wrong rows in plan |
| Previous Message | Scott Marlowe | 2010-03-29 06:45:44 | Re: Why Wal_buffer is 64KB |