On Mon, Jan 2, 2012 at 1:42 AM, chris r. wrote:
>>> I ported the entire schema to my test DB server and could not reproduce
>>> the error there. Note that probably recreating the view solves this
>>> issue. Given this, how should I proceed to create a test case? Any
>>> tutorial on this? (I'm not
>> I ported the entire schema to my test DB server and could not reproduce
>> the error there. Note that probably recreating the view solves this
>> issue. Given this, how should I proceed to create a test case? Any
>> tutorial on this? (I'm not too familiar with all this yet.)
>
> It's possibly s
"chris r." writes:
>> Nothing; that looks like a planner bug to me. Please submit a
>> self-contained test case.
> I ported the entire schema to my test DB server and could not reproduce
> the error there. Note that probably recreating the view solves this
> issue. Given this, how should I proce
>> So, you tell me, what's wrong with the old view?
>
> Nothing; that looks like a planner bug to me. Please submit a
> self-contained test case.
I ported the entire schema to my test DB server and could not reproduce
the error there. Note that probably recreating the view solves this
issue. Give
"chris r." writes:
> So, you tell me, what's wrong with the old view?
Nothing; that looks like a planner bug to me. Please submit a
self-contained test case.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
Hi all,
When SELECTing from one particular view, I get reproducible SEGFAULTs in
my pg 9.1.2 production database. To test for hardware errors, I ran
memtest, which succeeded. I then asked for help in #postgres and got
advice to create stacktraces, but I couldn't find the problem yet.
Scenario: VI
