Hello,
Need help on below error after upgrading the postgres from version to 12 to
13.7 I am trying to execute update_extensions.sql script and it throws an
error stating
ERROR: extension "plpgsql_check" has no update path from version "1.2" to
version "1.16". Please help me to fix it.
--
Shash
Hi
ne 3. 7. 2022 v 11:39 odesÃlatel shashidhar Reddy <
shashidharreddy...@gmail.com> napsal:
> Hello,
>
> Need help on below error after upgrading the postgres from version to 12
> to 13.7 I am trying to execute update_extensions.sql script and it throws
> an error stating
> ERROR: extension "pl
On Mon, Jun 20, 2022 at 9:53 PM Christoph Berg
wrote:
> IBM's reply to the issue back in December 2020 was this:
>
> The man page / infocenter document is not intended as an exhaustive
> list of all possible error codes returned and their circumstances.
> "Resource temporarily unavailable" m
I am a student who are interesting in database kernel.When I am
reviewing my database course,a question make me confused.
In file system,if a error happen when I insert some data into data
saving system,the whole data exists will be broken and can't recovery
anymore.
But when I check the cod
On 7/3/22 20:06, Wen Yi wrote:
I am a student who are interesting in database kernel.When I am
reviewing my database course,a question make me confused.
In file system,if a error happen when I insert some data into data
saving system,the whole data exists will be broken and can't recovery
any
Wen Yi writes:
> Since it's all built on top of the file system,why it always make sure
> that the postgres better than common csv file storage in disaster
> recovery?
Sure, Postgres cannot be any more reliable than the filesystem it's
sitting on top of (nor the physical storage underneath that