Hi folks —
We’ve got several tables that are relatively large (~250-500GB in total size)
that use very large (tens to hundreds of GB) GIN indexes for full-text search.
We’ve set the column statistics for our tsvector columns as high as they go
(10,000). We almost always order our search results
What if we just didn’t use positional arguments at all? I.e. we just populate
the tsvector with lexemes only?
> On Jun 20, 2018, at 10:49 AM, Tom Lane wrote:
>
> Jonathan Marks writes:
>> ... we run into the max tsvector length requirement "The length of a
>> tsv
Hi folks —
We utilize Postgres’ full text search system pretty heavily in our team’s
operations and often index tens of millions of records with varying lengths of
text. In most cases, the text we need to index is pretty short (no more than.
hundreds of words) but in rare cases a single record
Thank you so very much, Tom.
Vacuuming fixed the TOAST corruption issue and we’ll upgrade our instances
tonight (max RDS has is 10.3, but that’s a start).
> On Jun 5, 2018, at 8:07 PM, Tom Lane wrote:
>
> Jonathan Marks writes:
>> We had two issues today (once this morning
Hello —
We had two issues today (once this morning and once a few minutes ago) with our
primary database (RDS running 10.1, 32 cores, 240 GB RAM, 5TB total disk space,
20k PIOPS) where the database suddenly crashed and went into recovery mode. The
first time this happened, we restarted the serv
abase from a
> dump (yes you’ll need to create one from RDS because they don’t provide
> direct access to dumps/backups; probably you need to get only specific
> tables) and repeat your actions, closely looking at filesystem.
>
> ср, 16 мая 2018 г. в 13:10, Jonathan Marks <mailt
can run that might further
illuminate the issue?
Thank you!
> On May 14, 2018, at 3:31 PM, Jonathan Marks
> wrote:
>
> We’ll turn on log_temp_files and get back to you to see if that’s the cause.
> Re: the exact queries — these are just normal INSERTs and UPDATEs. This
>
files for a while, but we’re not sure what we should
do if that turns out to be the case.
> On May 14, 2018, at 3:08 PM, Tom Lane wrote:
>
> [ please keep the list cc'd ]
>
> Jonathan Marks writes:
>> Thanks for your quick reply. Here’s a bit more information:
>>
Hello!
We have a mid-sized database on RDS running 10.1 (32 cores, 240 GB RAM, 5TB
total disk space, 20k PIOPS) with several large (100GB+, tens of millions of
rows) tables that use GIN indexes for full-text search. We at times need to
index very large (hundreds of pages) documents and as a res
