Skip to content

Autovacuum after large update, with active RUM index crashes postgres  #19

Closed
@poppingtonic

Description

@poppingtonic

table with 160k records

UPDATE {table_name} SET {document}=data.{document} FROM
(VALUES %s) AS data ({document}, id)
WHERE {table_name}.id=data.id;

UPDATE {table_name} set {document_vector}=(select to_tsvector({document}));

CREATE INDEX {table_name}_rum_index
ON {table_name} USING RUM ({document_vector} rum_tsvector_ops);

After this set of queries, the autovacuum consumes all available memory before it crashes.

screenshot from 2017-05-30 10-41-09

Activity

za-arthur

za-arthur commented on May 30, 2017

@za-arthur
Contributor

Thank you for the issue! Will check.

za-arthur

za-arthur commented on May 30, 2017

@za-arthur
Contributor

Can you provide a backtrace please?

za-arthur

za-arthur commented on May 31, 2017

@za-arthur
Contributor

I reproduced it. Work on it.

poppingtonic

poppingtonic commented on May 31, 2017

@poppingtonic
Author

I took too long to get a backtrace, since my machine would lock up. Glad you reproduced it.

added a commit that references this issue on Jun 1, 2017

Issue #19. Bug in vacuuming.

za-arthur

za-arthur commented on Jun 1, 2017

@za-arthur
Contributor

I fixed the bug. Can you check it?

added a commit that references this issue on Jun 1, 2017
poppingtonic

poppingtonic commented on Jun 1, 2017

@poppingtonic
Author

Nice work! I ran it while watching htop, and autovacuum topped out at 5% memory right before it stopped.

za-arthur

za-arthur commented on Jun 1, 2017

@za-arthur
Contributor

Great!

added a commit that references this issue on Nov 1, 2017

Issue #19. Fix README.md. In that old README ts_rank() was used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @poppingtonic@za-arthur

        Issue actions

          Autovacuum after large update, with active RUM index crashes postgres · Issue #19 · postgrespro/rum