=?UTF-8?q?Mart=C3=ADn_Fern=C3=A1ndez?= writes:
> We are experiencing some `vacuum` issues with a given table (potentially
> more). When a manual vacuum runs on the given table it seems that the
> `vacuum` process is not doing the expected cleanup.
> DETAIL: 113257 dead row versions cannot be r
On Fri, 14 Sep 2018 18:29:27 -0400,
Tom Lane wrote:
> "Sebastian P. Luque" writes:
>> Tom Lane wrote:
>>> Personally, I'd probably write it something like this:
>>> select pa.attnum, pa.attname, col_description(pa.attrelid,
>>> pa.attnum) from pg_attribute pa, pg_attribute ta where pa.attrelid
Tom Lane writes:
> =?UTF-8?q?Mart=C3=ADn_Fern=C3=A1ndez?= writes:
>
>> We are experiencing some `vacuum` issues with a given table
>> (potentially more). When a manual vacuum runs on the given table it
>> seems that the `vacuum` process is not doing the expected cleanup.
>
>> DETAIL: 113257 dea
The preceding's pretty simple. An attacker goes after an individual,
> presumably without provocation and/or asymetrically. The attacked
> person is on this mailing list. IMHO this attacker must choose between
> continuing his attacks, and belonging to the Postgres community.
>
> What's tougher is
On Sat, Sep 15, 2018 at 4:47 AM James Keener wrote:
>
>
> The preceding's pretty simple. An attacker goes after an individual,
>> presumably without provocation and/or asymetrically. The attacked
>> person is on this mailing list. IMHO this attacker must choose between
>> continuing his attacks,
101 - 105 of 105 matches
Mail list logo