Re: logical replication snapshots

On 07/25/2018 11:10 AM, Dimitri Maziuk wrote:
> On 07/25/2018 11:16 AM, Adrian Klaver wrote:
> 
>> Where you using pg_export_snapshot() by any chance?:
> 
> If it's not in chapter 31 of TFM then I have not touched it. The only
> notable thing I changed from 31.9 quickstart is that replica identity is
> full on all tables (the data's a mess).
> 
>> Where there any relevant error messages in the log before the database
>> hung?
> 
> Do you seriously expect me to know what "relevant" is? ;) -- It's 7
> days' worth of
> 
>> 2018-07-23 09:43:12.851 CDT [7975] STATEMENT:  COPY macromolecules."Entity_common_name" TO STDOUT
>> 2018-07-23 09:43:12.925 CDT [7982] LOG:  logical decoding found consistent point at 19/E6942408
>> 2018-07-23 09:43:12.925 CDT [7982] DETAIL:  There are no running transactions.
>> 2018-07-23 09:43:12.935 CDT [7982] ERROR:  permission denied for schema macromolecules
>> 2018-07-23 09:43:12.935 CDT [7982] STATEMENT:  COPY macromolecules."Assembly" TO STDOUT
>> 2018-07-23 09:43:13.034 CDT [7987] LOG:  logical decoding found consistent point at 19/E6942440
>> 2018-07-23 09:43:13.034 CDT [7987] DETAIL:  There are no running transactions.
>> 2018-07-23 09:43:13.044 CDT [7987] ERROR:  permission denied for schema macromolecules
>> 2018-07-23 09:43:13.044 CDT [7987] STATEMENT:  COPY macromolecules."Spectral_transition" TO STDOUT
>> 2018-07-23 09:43:13.135 CDT [7990] LOG:  logical decoding found consistent point at 19/E6942478
>> 2018-07-23 09:43:13.135 CDT [7990] DETAIL:  There are no running transactions.
>> 2018-07-23 09:43:13.145 CDT [7990] ERROR:  permission denied for schema macromolecules
>> 2018-07-23 09:43:13.145 CDT [7990] STATEMENT:  COPY macromolecules."Assembly_db_link" TO STDOUT

A little slow, but I realized that the above looks like the initial sync 
for a table. Do these errors stretch back all the way back to your 
original sync?



> 
> that ends with
> 
>> 2018-07-23 09:45:40.280 CDT [6032] LOG:  database system was interrupted; last known up at 2018-07-06 17:04:28 CDT
>> 2018-07-23 09:45:40.281 CDT [6033] FATAL:  the database system is starting up
>> 2018-07-23 09:45:40.282 CDT [6034] FATAL:  the database system is starting up
> ... ad infinitum ...
> 
> Would "permission denied" be relevant?
> 
> (Not sure where that is coming from: I did initial sync as postgres then
> altered it to replication user. Can't track it down now since the
> database is dead.)
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com