Timescaledb: Running ALTER EXTENSION UPDATE while already running latest version

[Ormod]

Relevant system information:

• TimescaleDB version (output of \dx in psql): 1.0.1
• Installation method: [e.g., "using Docker", "apt install", "source"]

Describe the bug
Running ALTER EXTENSION UPDATE on an already created extension that's running the latest version causes an error to be returned:

defaultdb=> alter extension timescaledb update;
ERROR: extension "timescaledb" cannot be updated after the old version has already been loaded
HINT: Start a new session and execute ALTER EXTENSION as the first command. Make sure to pass the "-X" flag to psql.
A clear and concise description of what the bug is.

Note that in this case it was the first command issued on a new PG session.

Expected behavior
The default PG extension behavior is to always give out just a NOTICE.

[svenklemm]

@Ormod Is this still happening on 1.2.x? I can't reproduce:

%  psql -h localhost gapfill -X -c 'ALTER EXTENSION timescaledb UPDATE;'
NOTICE:  version "1.3.0-dev" of extension "timescaledb" is already installed
ALTER EXTENSION

[cevian]

@svenklemm does it give an error if -X isn't passed in to psql?

[vdedyukhin]

This message appears after typing, for example, '\dx' command before ALTER EXTENSION timescaledb UPDATE;

[henrych4]

Not sure if it helps:

In my case, running docker exec -it ${containerName} sh first, then start instance by running psql -U postgres -X and finally execute ALTER EXTENSION timescaledb UPDATE; leads to error message "ERROR: extension "timescaledb" cannot be updated after the old version has already been loaded ..."

To make it works, the first two commands have to be executed in single line:
docker exec -it ${containerName} psql -U postgres -X. Then executing the ALTER command updates extension.

[cevian]

I think this has been fixed a while ago, please let me know if not.

[jaalsuca]

I currently experiencing the error. Someone can help me out!
ERROR: extension "timescaledb" has already been loaded with another version
DETAIL: The loaded version is "1.6.0".
HINT: Start a new session and execute CREATE EXTENSION as the first command. Make sure to pass the "-X" flag to psql.
SQL state: 42710

[dberardo]

same problem here ... and of course if i try to kill the postgres service before running the command, then psql cannot even run .... sounds like a vicious circle :D