| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Tim Uckun <timuckun(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Getting TOAST errors |
| Date: | 2011-09-20 00:01:58 |
| Message-ID: | 25126.1316476918@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tim Uckun <timuckun(at)gmail(dot)com> writes:
>> Well, I'm not asking for perfect reproducibility --- a test case that
>> fails even 1% of the time would be great.
> What exactly do you need?
A self-contained test case (code and data) that triggers the error.
If it only does so probabilistically, once in every-so-many runs,
that's fine.
> The database is not too large but the data is proprietary. Despite
> this I am willing to provide a sampling of the data in the two tables
> involved.
Perhaps you could sanitize or anonymize the data? It's unlikely that a
bug of this sort has all that much to do with the exact data content.
Whether the bug would still show for a "sample" is a different question,
and one you'd have to resolve by experiment.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Uckun | 2011-09-20 00:07:52 | Re: Getting TOAST errors |
| Previous Message | Tim Uckun | 2011-09-19 23:57:22 | Re: Getting TOAST errors |