:
On 12/02/2014 03:50 PM, Joshua Boyd wrote:
Having continued my research, the problem I encountered is the exact
same that's been recorded here:
https://www.marshut.net/kstxxk/pitr-failing-to-stop-
before-drop-database.html
I think I answered all the questions - please let me know if I
I pasted at the top, though, it appears I'm not the
only one who's encountered this problem.
On Tue, Dec 2, 2014 at 3:39 PM, Adrian Klaver adrian.kla...@aklaver.com
wrote:
On 11/28/2014 02:29 PM, Joshua Boyd wrote:
I am testing out point in time recovery from a hot physical backup
of
transaction 235078 ... it doesn't appear that it's 100% accurate. It
didn't commit the transaction, clearly, because the database is still
listed in the data dictionary ... however, the filesystem files are gone.
Please - am I doing something wrong, or would this be considered a bug?
--
Joshua Boyd
Ah - that's what unpackaged meant. I read that page, but didn’t fully
understand what it was referring to. Thank you for your quick reply. :)
Josh
-Original Message-
From: Kevin Grittner [mailto:kgri...@ymail.com]
Sent: Friday, November 22, 2013 1:21 PM
To: Joshua Boyd; pgsql
We have a pre-production environment that was running postgresql 9.0 and we
created the extension pgcrypto in it by feeding psql the contrib/pgcrypto.sql
.. We just upgraded to 9.2 (via pg_upgrade) - naturally all the functions
still exist, but pgcrypto is not a registered extension with the
