Hi,
I upgraded my cluster from 9.6 to 11 with pg_upgrade hardlink parameter two
days ago. Since then it has been working great as v11. Today while running
heavy update queries on it, I got the "FATAL: invalid page in block 0 of
relation global/1262" message and server crushed.
Hard reset and tryi
Hi Vikas,
For the postgres service, we have the same case (each cluster members has
different minor version of 9.6) and there is no problem with that.
But be careful about extensions. Because sometimes an extension can require
an upgrade in its db structure otherwise it won't work. So if there is a
Hi Tim,
There are good continuously running apps to monitor postgres.
IMHO, the most successful one is pgcenter.
Here is the link. https://github.com/lesovsky/pgcenter
Regards
İbrahim
On 16 Feb 2018 5:22 am, "Tim Cross" wrote:
> Hi All,
>
> I was wondering if anyone has some pointers to
> site
Hi Tim,
You have to enable hot_standby=on parameter on the replica server. See the
below link.
https://wiki.postgresql.org/wiki/Hot_Standby
Regards,
Ibrahim.
2018-01-30 21:16 GMT+03:00 Tim Bowden :
> I've inherited a PG 9.4.4 install on Win 2008 that I'm wanting to
> stream from (abt 80Gb on dis
Hi,
In our environment, we are logging "all" statements because of the security
considerations (future auditing if necessary). But the system is very big
and produces 100GB logs for an hour and we expect that this will be much
more. We are having trouble to find the disk for this amount of data.
N
hi Peter,
today, we took the dump of database and restored to another empty cluster
and run the queries on it for test purposes, no problem at all. All errors
are gone.
>
> > As I mentioned earlier, if this takes too long, you could only do
> > heapallindexed checking once per table (not once per index) by giving
> > "indisprimary" as the heapallindexed argument. That way, only primary
> > keys would be verified against the heap, which is potentially a lot
> > fas
GMT+03:00 Peter Geoghegan :
> On Sun, Dec 31, 2017 at 1:50 PM, Ibrahim Edib Kokdemir
> wrote:> * write_cache is disabled
> > * there is no incorrect work_mem parameter setting.
> > * logical dump is working, (maybe) no curruption in data.
> > * there is streaming replic
Hi,
We are getting same error a lot for more than 1 days from different schemas
in the same db.
< user=myuser db=mydb host=mydbip pid=18883 app=[unknown] time=2017-12-31
14:28:16.056 +03 > ERROR: invalid memory alloc request size
576460752438159360
CentOS Linux release 7.4.1708 (Core)
DB version
