On Wed, 2019-05-08 at 12:42 -0700, Adrian Klaver wrote:
> At this point I would say your are going to need to go back to the last
> clean backup and restore from there into a clean instance of Postgres on
> a clean version of whatever OS you are running on.
... and of course, plug the hole throu
On 5/8/19 9:04 AM, Prashant Hunnure wrote:
Please reply to list also.
Ccing list.
Hi Adrian,
Thanks for the reply.
As my public schema under the said database has been renamed by public
bla bla bla.and the .map file from the global folder is in encrypted
format.
At this point I would s
On 5/8/19 3:42 AM, Prashant Hunnure wrote:
Dear Team,
I am working on postgres database version 9.3 is the part of opengeo
suite and now my running database become hacked by someone. In the
What makes you think it was hacked?
current situation I'm able to view my database under Pgadmin III
On 5/8/19 5:42 AM, Prashant Hunnure wrote:
Dear Team,
I am working on postgres database version 9.3 is the part of opengeo suite
and now my running database become hacked by someone. In the current
situation I'm able to view my database under Pgadmin III but unable to
view the tables, functio
> I am working on postgres database version 9.3
> ...and now my running database become hacked by someone.
imho:
The 9.3 version is End of Life (EoL) ;
Final Release:9.3.25 (November 8, 2018)
https://www.postgresql.org/support/versioning/
Please upgrade for newer versions ( with the latest
Dear Team,
I am working on postgres database version 9.3 is the part of opengeo suite
and now my running database become hacked by someone. In the current
situation I'm able to view my database under Pgadmin III but unable to view
the tables, functions and other attributes on windows environment.
