| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | chris(at)chriscurvey(dot)com, pgsql <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: "could not split GIN page; no new items fit" |
| Date: | 2015-04-08 04:58:47 |
| Message-ID: | 24411.1428469127@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> writes:
> On 4/4/15 8:38 AM, Chris Curvey wrote:
>> I can! I just copied the data to a new table, obfuscated the sensitive
>> parts, and was able to reproduce the error. I can supply the script to
>> create and populate the table, but that's still clocking in at 250Mb
>> after being zipped. What's the best way of getting this data out to
>> someone who can take a look at this? (Feel free to contact me off-list
>> to coordinate.)
> It would be nice if you could further reduce it, but if not I'd suggest
> posting it to something like DropBox and posting the public link here.
So far I've been unable to reproduce the failure from Chris' data :-(
Don't know why not.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2015-04-08 05:14:16 | Re: "could not split GIN page; no new items fit" |
| Previous Message | Jim Nasby | 2015-04-08 04:44:08 | Re: "could not split GIN page; no new items fit" |