On Tue, Feb 22, 2022 at 12:27 PM Torsten Förtsch
wrote:
> Hi,
>
> I have a few databases with several TB-sized tables. We recently moved one
> of those databases from AWS EC2 to GCP. Today I ran VACUUM FREEZE on those
> tables and every time I saw our application freezing up (and throwing tons
>
On 2/22/22 12:27, Torsten Förtsch wrote:
Hi,
I have a few databases with several TB-sized tables. We recently moved
one of those databases from AWS EC2 to GCP. Today I ran VACUUM FREEZE on
those tables and every time I saw our application freezing up (and
throwing tons of errors) for a few mi
Hi,
I have a few databases with several TB-sized tables. We recently moved one
of those databases from AWS EC2 to GCP. Today I ran VACUUM FREEZE on those
tables and every time I saw our application freezing up (and throwing tons
of errors) for a few minutes right after the message about the end of
Allan Jardine writes:
> => select to_tsquery('all:*');
> NOTICE: text-search query contains only stop words or doesn't contain
> lexemes, ignored
> to_tsquery
>
> (1 row)
> I get why that is happening - the notification basically details it, but
> the wildcard at the end seems to m
Hi all,
I'm venturing into full text search in Postgres for the first time, and I'd
like to be able to do a search by the start of a word - so I used the `:*`
operator. However, this doesn't operate as I'd expect with a stop word -
for example, my name is "Allan" so I often use it as a test string
