Professional Web Applications Themes

vacuum is failing - PostgreSQL / PGSQL

I've got a server running PostgreSQL-7.2.3 on RHAS-2.1. The version of Postgresql is *not* my choice, I would have gone with something much more current, but i digress. Running 'vacuumdb -a -z -v -f' has started failing: NOTICE: Index pg_toast_218644531_idx: Pages 1; Tuples 0. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: yzing doc2_review_comments NOTICE: --Relation groups-- NOTICE: Pages 28: Changed 0, reaped 2, Empty 0, New 0; Tup 331: Vac 2, Keep/VTL 0/0, UnUsed 1, MinLen 160, MaxLen 1988; Re-using: Free/Avail. Space 13360/12448; EndEmpty/Avail. Pages 0/17. CPU 0.01s/0.00u sec elapsed 0.07 sec. NOTICE: Index grps: Pages 2; Tuples 331: Deleted ...

  1. #1

    Default vacuum is failing

    I've got a server running PostgreSQL-7.2.3 on RHAS-2.1. The version
    of Postgresql is *not* my choice, I would have gone with something
    much more current, but i digress.

    Running 'vacuumdb -a -z -v -f' has started failing:

    NOTICE: Index pg_toast_218644531_idx: Pages 1; Tuples 0.
    CPU 0.00s/0.00u sec elapsed 0.00 sec.
    NOTICE: yzing doc2_review_comments
    NOTICE: --Relation groups--
    NOTICE: Pages 28: Changed 0, reaped 2, Empty 0, New 0; Tup 331: Vac
    2, Keep/VTL 0/0, UnUsed 1, MinLen 160, MaxLen 1988; Re-using:
    Free/Avail. Space 13360/12448; EndEmpty/Avail. Pages 0/17.
    CPU 0.01s/0.00u sec elapsed 0.07 sec.
    NOTICE: Index grps: Pages 2; Tuples 331: Deleted 2.
    CPU 0.00s/0.00u sec elapsed 0.00 sec.
    NOTICE: Index groups_public: Pages 2; Tuples 331: Deleted 2.
    CPU 0.00s/0.00u sec elapsed 0.02 sec.
    NOTICE: Index groups_status: Pages 2; Tuples 331: Deleted 2.
    CPU 0.00s/0.00u sec elapsed 0.00 sec.
    NOTICE: Index groups_type: Pages 2; Tuples 331: Deleted 2.
    CPU 0.00s/0.00u sec elapsed 0.00 sec.
    NOTICE: Index group_unix_uniq: Pages 4; Tuples 331: Deleted 2.
    CPU 0.00s/0.00u sec elapsed 0.00 sec.
    ERROR: No one parent tuple was found


    Anyone have any suggestions on how to correct this? This DB serves a
    web based PHP application, and right now there isn't any end user
    noticable problems, and i'd like to keep it that way :)

    thanks in advance!

    --
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~
    L. Friedman [email]netllama[/email]
    LlamaLand [url]http://netllama.linux-sxs.org[/url]

    ---------------------------(end of broadcast)---------------------------
    TIP 8: explain yze is your friend

    Lonni J Friedman Guest

  2. #2

    Default Re: vacuum is failing

    Lonni J Friedman <netllama> writes:
    > ERROR: No one parent tuple was found
    > Anyone have any suggestions on how to correct this?
    Shut down whatever long-running transaction is hanging around in the
    background. You wouldn't be getting this error if vacuum weren't
    trying to move a chain of updated tuples, and that can only happen
    if there's an old transaction someplace.

    Of course, the real fix is to use a newer Postgres. I note this in
    the 7.2.4 CVS logs:

    2003-01-26 18:09 tgl

    * src/backend/access/heap/heapam.c (REL7_2_STABLE): Back-patch
    fixes to ensure t_ctid always has correct value (prevents some
    instances of 'No one parent tuple' VACUUM error, and perhaps worse
    things).

    regards, tom lane

    ---------------------------(end of broadcast)---------------------------
    TIP 5: Have you checked our extensive FAQ?

    [url]http://www.postgresql.org/docs/faqs/FAQ.html[/url]

    Tom Lane Guest

  3. #3

    Default Re: vacuum is failing

    On Tue, 04 Jan 2005 18:30:43 -0500, Tom Lane <tglsss.pgh.pa.us> wrote:
    > Lonni J Friedman <netllama> writes:
    > > ERROR: No one parent tuple was found
    >
    > > Anyone have any suggestions on how to correct this?
    >
    > Shut down whatever long-running transaction is hanging around in the
    > background. You wouldn't be getting this error if vacuum weren't
    > trying to move a chain of updated tuples, and that can only happen
    > if there's an old transaction someplace.
    >
    > Of course, the real fix is to use a newer Postgres. I note this in
    > the 7.2.4 CVS logs:
    >
    > 2003-01-26 18:09 tgl
    >
    > * src/backend/access/heap/heapam.c (REL7_2_STABLE): Back-patch
    > fixes to ensure t_ctid always has correct value (prevents some
    > instances of 'No one parent tuple' VACUUM error, and perhaps worse
    > things).
    Thanks Tom. I should have googled first, cause this seems to have
    come up alot before 7.2.4 was released. I'll schedule some down time
    and see if running vacuum fixes this (temporarily). Getting
    postgresql upgraded might require an act of $DEITY *sigh*

    --
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~
    L. Friedman [email]netllama[/email]
    LlamaLand [url]http://netllama.linux-sxs.org[/url]

    ---------------------------(end of broadcast)---------------------------
    TIP 3: if posting/reading through Usenet, please send an appropriate
    subscribe-nomail command to [email]majordomopostgresql.org[/email] so that your
    message can get through to the mailing list cleanly

    Lonni J Friedman Guest

Similar Threads

  1. vacuum vs open transactions
    By Ed L. in forum PostgreSQL / PGSQL
    Replies: 15
    Last Post: January 13th, 07:23 PM
  2. replacements for vacuum?
    By Lonni J Friedman in forum PostgreSQL / PGSQL
    Replies: 6
    Last Post: December 18th, 07:25 AM
  3. VACUUM FULL [YZE] problem
    By Tim Vadnais in forum PostgreSQL / PGSQL
    Replies: 3
    Last Post: December 15th, 09:25 PM
  4. Deadlock detected during vacuum yze
    By Egyd Csaba in forum PostgreSQL / PGSQL
    Replies: 0
    Last Post: December 14th, 07:23 PM
  5. vacuum problem?
    By Ed L. in forum PostgreSQL / PGSQL
    Replies: 2
    Last Post: December 10th, 10:55 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139