From: | Vick Khera <vivek(at)khera(dot)org> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Jira database won't start after disk filled up |
Date: | 2018-03-04 16:45:28 |
Message-ID: | CALd+dccRgJQQuZ92PC8FZnsOD7C1Nk+KBcKFE7tyF2pFDOo8Dg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Mar 2, 2018 at 5:13 PM, Paul Costello <paulc1217(at)gmail(dot)com> wrote:
> My hope is that I can get the db back to 1/10 and maybe we can, with
> Atlassian's help, somehow sync the lucene files back to the db. I don't
> think I will have any postgres data to work with beyond 1/10.
>
> Does this still sound do-able with that kind of data gap?
>
>
I'm not sure how the incremental updates to the lucene indexes work with
Jira. If they are parallel to writing to the DB maybe you can recover some
info there; if they are trickled out asynchronously after writing to the DB
by an index process that reads back the DB, then I'd expect there to be no
additional info there.
Perhaps the best you can do is get Jira to run its integrity checker on the
current data and fix whatever it tells you to fix. I think Atlassian will
know best.
From | Date | Subject | |
---|---|---|---|
Next Message | Albrecht Dreß | 2018-03-04 17:48:10 | Q: text palloc() size vs. SET_VARSIZE() |
Previous Message | Tom Lane | 2018-03-03 15:30:12 | Re: pg_upgrade fails to restore function |