From: | J Smith <dark(dot)panda+lists(at)gmail(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Errors on missing pg_subtrans/ files with 9.3 |
Date: | 2013-11-12 17:17:03 |
Message-ID: | CADFUPgfqPiazOauuM7M-qfwA5SWqwQ9mHevRB5kh0A1Lm8-w=g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Nov 12, 2013 at 11:54 AM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
>
> Did you also upgrade to PostGIS 2.x as part of this..? Seems like it'd
> be unrelated, but one never knows. Any chance you could distill this
> down into a small test case which exhibits the problem? I'm guessing
> 'no', but figured I'd ask anyway..
>
Yeah, we upgraded to PostGIS 2.1 as part of the upgrade. In the case
of the specific database that is exhibiting the problem, we only
really use PostGIS for storage and don't do a lot of spatial querying,
as this database is basically for an aggregation service we run. In
the case of the transactions that appear to be causing the problems,
we don't even use geometry fields at all.
Cheers
From | Date | Subject | |
---|---|---|---|
Next Message | Kohei KaiGai | 2013-11-12 17:22:59 | Re: What's needed for cache-only table scan? |
Previous Message | Robert Haas | 2013-11-12 17:13:54 | Re: logical changeset generation v6.6 |