| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Rob Sargent <robjsargent(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: gin index trouble |
| Date: | 2017-10-30 16:23:18 |
| Message-ID: | 3466.1509380598@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Rob Sargent <robjsargent(at)gmail(dot)com> writes:
>> If you can make a test case that (eventually) hits that, we'd be
>> interested to see it ...
> Any hint(s) on what might trigger this sort of thing? I could duplicate
> the upload, but I doubt you want the 800K records, 200M input file even
> if it did regenerate the problem.
It's possible you could duplicate the failure with synthetic data
generated by a not-very-long script. That would beat uploading
a large data file, not to mention possibly needing to sanitize
your data.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adam Brusselback | 2017-10-30 16:29:03 | UPDATE syntax change |
| Previous Message | Peter Geoghegan | 2017-10-30 16:15:38 | Re: gin index trouble |