oldest xmin is far in the past

Поиск
Список
Период
Сортировка
От John Snow
Тема oldest xmin is far in the past
Дата
Msg-id CAM+o-ApLaXFLaieaVx5Dj1RKCx2OaLm5akJ909j8H8FLL5UJMg@mail.gmail.com
обсуждение исходный текст
Ответы Re: oldest xmin is far in the past  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
Список pgsql-hackers
Hi everyone!

Trying to make VACUUM FREEZE on PG instance and keep getting this error:

2016-03-18 05:56:51 UTC   46750 WARNING:  oldest xmin is far in the past
2016-03-18 05:56:51 UTC   46750 HINT:  Close open transactions soon to avoid wraparound problems.
2016-03-18 05:56:51 UTC   46750 DEBUG:  transaction ID wrap limit is 2654342112, limited by database with OID 1
2016-03-18 05:56:51 UTC   46750 DEBUG:  MultiXactId wrap limit is 2147483648, limited by database with OID 12451

Also "age" and "relfrozenxid" doesnt't change.

I will show what I'm trying to do step by step:

Executing this command:
SELECT
pg_namespace.nspname
,c.relname AS relname
--,c.oid::regclass as table_name
,greatest(age(c.relfrozenxid),age(t.relfrozenxid)) as age
,c.relfrozenxid
,t.relfrozenxid
FROM pg_class c
LEFT JOIN pg_class t ON c.reltoastrelid = t.oid
LEFT JOIN
pg_namespace
ON pg_namespace.oid = c.relnamespace
WHERE c.relkind = 'r'
ORDER BY
age desc
,1,2;
Output looks like this:
nspname relname age relfrozenxid relfrozenxid
public action_flows 543567979 506858465 506858465
public advertiser_requests 543567979 506858465 506858465
public authtokens 543567979 506858465 506858465
public blacklist 543567979 506858465 506858465
public blog_categories 543567979 506858465 506858465
public blog_posts 543567979 506858465 506858465
public bp_service_codes 543567979 506858465 506858465
public browsers 543567979 506858465 506858465
Then I'm doing: VACUUM FREEZE; and nothing happens, I only get debug and warning messages as I mentioned above.

Settings on server:

namesettingunit
autovacuumon
autovacuum_analyze_scale_factor0.1
autovacuum_max_workers20
autovacuum_vacuum_cost_delay0ms
autovacuum_vacuum_cost_limit200
autovacuum_vacuum_scale_factor0.2
bgwriter_delay200ms
checkpoint_completion_target0.9
checkpoint_segments128
checkpoint_timeout1800s
client_encodingUTF8
client_min_messagesdebug1
commit_delay5000
commit_siblings15
DateStyleISO, MDY
deadlock_timeout1000ms
debug_pretty_printon
default_statistics_target100
default_text_search_configpg_catalog.english
dynamic_shared_memory_typeposix
effective_cache_size125829128kB
extra_float_digits3
fsyncon
full_page_writesoff
lc_messagesen_US.UTF-8
lc_monetaryen_US.UTF-8
lc_numericen_US.UTF-8
lc_timeen_US.UTF-8
listen_addresses*
log_autovacuum_min_duration1000ms
log_checkpointson
log_destinationstderr
log_directory/home/pgsql/data/pg_log
log_filenamepostgresql-%a.log
log_line_prefix%t %h %u %p
log_lock_waitson
log_min_duration_statement1000ms
log_min_error_statementdebug1
log_min_messagesdebug1
log_rotation_age1440min
log_rotation_size0kB
log_statementnone
log_timezoneUTC
log_truncate_on_rotationon
logging_collectoron
maintenance_work_mem2097152kB
max_connections800
max_prepared_transactions10
max_replication_slots1
max_stack_depth2048kB
max_wal_senders3
port9125
random_page_cost1.2
search_pathpublic
seq_page_cost1
shared_buffers65536008kB
synchronous_commitoff
temp_buffers163848kB
TimeZoneEurope/Moscow
track_countson
update_process_titleoff
vacuum_cost_delay1ms
vacuum_freeze_min_age75000000
vacuum_freeze_table_age200000000
vacuum_multixact_freeze_min_age5000000
vacuum_multixact_freeze_table_age150000000
wal_buffers20488kB
wal_keep_segments128
wal_levelhot_standby
work_mem65536kB

Also:
select txid_current(); - 5345750425
select xmin from stats_y2016_m3 order by ts_spawn desc limit 1; - 1050801875
why such difference?

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: Parallel Aggregate
Следующее
От: Robert Haas
Дата:
Сообщение: Re: Parallel Aggregate