Open ManuelLR opened 5 years ago
Default log only by stdout (I don't know what the current behaviour is)
Take into account that postgres has a log configuration which logs all SQL queries (log_statement = 'all'
), which I think is enabled by default.
This setting should be disabled by default, specially in production environments. It may be useful tough to in development environments.
Add unaccent
library from the contrib directory in order to be able to load as extension
tablefunc in order to pivot tables quickly.
Default log only by stdout (I don't know what the current behaviour is)
Take into account that postgres has a log configuration which logs all SQL queries (
log_statement = 'all'
), which I think is enabled by default.This setting should be disabled by default, specially in production environments. It may be useful tough to in development environments.
Maybe we could change log_statement
default value to ddl
in our Docker image.
Regarding to compile contrib extensions in default image I have some doubts. An alternative could be to document in main README how to add a contrib extension to your project Dockerfile extending from base image. What do you think about it?
It would be nice also to have a vi installed
It would be nice also to have a vim installed and delightful to have a minimal .vimrc (https://gist.github.com/vehrka/71b289bfe79854da0d92e8480bd42f15)
I think is better if the people install Vim (or his choice text editor) in a custom or project derived image so we can maintain base image (this image) thinner.
It would be nice also to have a vim installed and delightful to have a minimal .vimrc (https://gist.github.com/vehrka/71b289bfe79854da0d92e8480bd42f15)
I think is better if the people install Vim (or his choice text editor) in a custom or project derived image so we can maintain base image (this image) thinner.
(edited my original coment)
Except when you deploy behind a firewalled environment and you cannot install anything.
In the image there is NO editor at all, nothing not even nano ...
I agree with @cayetanobv, I think that it is not typical for docker images to have more than needed to run the target application/service in a context-less environment. This kind of software must be included in derived images.
PG_CONF
reloaded in every reboot