From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bridget Frey <bridget(dot)frey(at)redfin(dot)com> |
Cc: | Duncan Rance <postgres(at)dunquino(dot)com>, pgsql-bugs(at)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com> |
Subject: | Re: BUG #6425: Bus error in slot_deform_tuple |
Date: | 2012-02-03 07:47:15 |
Message-ID: | 13251.1328255235@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Bridget Frey <bridget(dot)frey(at)redfin(dot)com> writes:
> I just wanted to say thanks to everyone who has been working so hard on
> this issue. I realize it's not certain that this would fix the issues
> we're seeing, but we'd be willing to try it out and report back. The only
> caveat is we would need to deploy it to production, so if someone could let
> us know what the risk factor is here (e.g. the potential to make things
> worse), that would help us plan out how and when we would want to try it.
AFAICS the proposed patch is totally safe; it can't make things worse,
and should save some cycles to boot. Whether it fixes what you're
seeing is a different question of course, but testing would be mighty
helpful for that.
What I would actually ask about as far as production risk goes is
whether you are accustomed to building from patched sources. If you're
not, the risk of dropping a stitch in the build process could be
significant.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | giri.anamika0 | 2012-02-03 10:25:39 | BUG #6430: Wal Segment Size is 128GB |
Previous Message | Bridget Frey | 2012-02-03 07:27:38 | Re: BUG #6425: Bus error in slot_deform_tuple |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-02-03 08:49:38 | Re: [PATCH] Fix float8 parsing of denormal values (on some platforms?) |
Previous Message | Bridget Frey | 2012-02-03 07:27:38 | Re: BUG #6425: Bus error in slot_deform_tuple |