From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Nagaraj Raj <nagaraj(dot)sf(at)yahoo(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_repack failure |
Date: | 2020-01-07 06:46:12 |
Message-ID: | 20200107064612.GH2386@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Tue, Jan 07, 2020 at 06:15:09AM +0000, Nagaraj Raj wrote:
> and this error is occurring in large tables only, and current table
> size which is running about 700GB
>
> /pg_repack --version
> pg_repack 1.4.3
>
> DB version: PostgreSQL 9.6.11 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.9.3, 64-bit
I think that you had better report that directly to the maintainers of
the tool here:
https://github.com/reorg/pg_repack/
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2020-01-07 11:11:54 | Re: How to shorten a chain of logically replicated servers |
Previous Message | Nagaraj Raj | 2020-01-07 06:15:09 | pg_repack failure |
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro Horiguchi | 2020-01-07 06:57:29 | Re: Fetching timeline during recovery |
Previous Message | Amit Kapila | 2020-01-07 06:18:10 | Re: pgsql: Add basic TAP tests for psql's tab-completion logic. |