Fix it already, so it was the SAN and vmware issue.
Thanks Everyone.
On Fri, Jan 15, 2021 at 4:40 PM Soni M wrote:
> More disk space now available, but still the error happens and postgres
> won't start.
> I think it could be corrupted shared buffers, as stated on the log
&
13 +0700, Soni M wrote:
> > We filled out the wal archive disk, and then those messages appear
> >
> > [...]PANIC,58030,"could not fsync file ""pg_wal/xlogtemp.3510"":
> Input/output error"
> >
> > And now I cannot start postgres
> >
Hi All,
Postgres 11 on RHEL 7.9
We filled out the wal archive disk, and then those messages appear
2021-01-15 01:18:47.284
CST,"replicator","consprod",3510,"[local]",5fdebf22.db6,21,"SELECT",2020-12-19
21:04:02 CST,35/46792889,437317854,PANIC,58030,"could not fsync file
""pg_wal/xlogtemp.3510"": I
Hi All,
currently I'm trying to configure postgres (on centos) to load data from MS
SQL server (on windows server) on an encrypted connection.
Trying with tds_fdw, but found that it doesn't support encrypted connection.
Is there any solution to this?
Thanks,
Soni.
