On 2/8/20 2:24 PM, Marc wrote:
Adrian,
Old production server was postgres 9.6 with Mac0S 10.9 so much older
than the “new” server. ( Now MacOS 10.14 Postgres 12.1 )
After sudden restart of the cpu we started having issues, part of the
data that is lost TOAST. . . and we also started having issues when
TRUNCATING certain tables. The tabel where Nick reported the
“UPPER”-issue was not “involved”
The data we restored today on the “new” server was from before the
crash, and in our opinion “healthy”, didn’t run into any issue importing it.
Never had issues before, RAID system wasn’t giving any warnings neither.
We still presume an hardware failure, but haven’t been able to figure
out what exactly.
I’ll provide a log tomorrow in the morning CET.
Regarding the stack trace we’ll dig in to it to see what we can come up with
¿ is downgrading possible ? We need to have a working system by tomorrow
evening CET.
I assume you are talking about taking the data dumped from the 'healthy'
9.6 instance and loading it into an 11 instance?
It would be worth a try, but if you think there is version problem why
not just use a 9.6 instance for the new server?
If you still have issues, then:
1) Has someone created there own versions of lower() and upper() that
are masking the default ones?
2) The schema for the problem table, in particular the index definitions
for the problem fields.
3) Any recent changes/additions of extensions?
Thanks in advance,
Marc
On 8 Feb 2020, at 22:18, Adrian Klaver wrote:
On 2/8/20 12:28 PM, Marc wrote:
Adrian,
Everything was a clean install ( MacOS Mojave and Postgres )
Export and import were done with the latest version of PGAdmin.
Please advise if we can provide you with anything ( logging etc
. . . )
Is there a possibility to downgrade to version 11 ?
At this point hard to tell whether this a version issue or something
else. Probably best not to introduce too many more moving parts at
this time.
Questions:
1) The OS and version you mention above is the same as on the
production server below?
2) What where the exact issues you had on the production server?
The actual error messages would be very helpful.
3) Getting a stack trace of the UPPER(), LOWER() issue would be
nice. For more info on that:
Not that familiar with MacOS, so not sure if the Linux/BSD steps
would apply or not, still:
https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
We upgraded over the weekend because we experienced a crash on
our production server with “toast” issues as result.
Thanks in advance,
Marc
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
*ARC - your Apple Authorised Service partner* H.D. Saviolaan 8
B-1700 Dilbeek
Belgium
info@xxxxxxxxxx <mailto:info@xxxxxxxxxx> www.arcict.com
<http://www.arcict.com>
tel. : +32 (0)2 466 50 00 fax. : +32 (0)2 466 88 33
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
