| From: | dennis jenkins <dennis(dot)jenkins(dot)75(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: database error xx000? |
| Date: | 2012-04-26 19:07:42 |
| Message-ID: | CAAEzAp8CvV-S3GakmPaxsijVUz9z33fAgnr8PVNwhRJT87rAWw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Apr 26, 2012 at 1:59 PM, Kenneth Tilton <ktilton(at)mcna(dot)net> wrote:
> On Thu, Apr 26, 2012 at 2:24 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>
>> Can you produce a self-contained test case?
>>
>
> I doubt it. Every test iteration I run includes a lot of redefining of
> functions and triggers all over the map, and it works fine thru dozens of
> iterations. The wheels seem to come off after a serious refactoring.
> Nothing is needed to clear the problem except (it seems) close any
> connections to the DB, so I guess some optimization does not work in the
> face of sufficient dynamic redefinition.
>
>
>
Suggestion: create a program which attempts to stress-test Postgresql by
doing similar things. Even if a single test case does not reliably
reproduce the issue, a stress-test might trigger the condition after some
time.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Farber | 2012-04-26 19:45:15 | Which data type to use for UTF8 JSON and perl/PHP: varchar, text or bytea? |
| Previous Message | Kenneth Tilton | 2012-04-26 18:59:17 | Re: database error xx000? |