[13.2.0] columnar is disabled on image start

[victornoel]

Hi,

Because of citusdata/citus#8081, it seems that when running the docker image, since it's starting on an empty db, the columnar storage is disabled. It wasn't the case with the docker image for 13.1.0.

I think that for a docker image, it does not make sense to have this behaviour and that maybe the startup script should enable it explicitly.

Does it make sense?

[onurctirtir]

Hey,

citus_columnar can still be created via CREATE EXTENSION citus_columnar;, do you think this is a breaking change for you, or for other users?

[victornoel]

@onurctirtir well, it's a breaking change in the sense that anybody using this image in, e.g., CI test envs where you start with an empty db, is going to find it not working anymore if they need columnar storage.

Though if you think it's best to keep the default citus behaviour for the docker image, then maybe having an env-var based toggle to load it by default in the docker image could be cool? I'm thinking of CI systems where it's easy to add one more env var but not easy to execute a command on the db directly.

I guess it could also be the responsibility of the app (under test, or in production) to enable the extension if it's needed?

I honestly don't know what is reasonable and will be happy to adapt if the new behaviour is the desirable one :)