Timescale DB Warnings on new install
-
recently moved my netxms install to a new server and received the following when initializing the db
WARNING: column type "character varying" used for "idata_value" does not follow best practices
HINT: Use datatype TEXT instead.
WARNING: column type "character varying" used for "raw_value" does not follow best practices
HINT: Use datatype TEXT instead.
WARNING: column type "character varying" used for "idata_value" does not follow best practices
HINT: Use datatype TEXT instead.
WARNING: column type "character varying" used for "raw_value" does not follow best practices
HINT: Use datatype TEXT instead.
WARNING: column type "character varying" used for "idata_value" does not follow best practices
HINT: Use datatype TEXT instead.
WARNING: column type "character varying" used for "raw_value" does not follow best practices
HINT: Use datatype TEXT instead.
WARNING: column type "character varying" used for "idata_value" does not follow best practices
HINT: Use datatype TEXT instead.
WARNING: column type "character varying" used for "raw_value" does not follow best practices
HINT: Use datatype TEXT instead.
WARNING: column type "character varying" used for "idata_value" does not follow best practices
HINT: Use datatype TEXT instead.
WARNING: column type "character varying" used for "raw_value" does not follow best practices
HINT: Use datatype TEXT instead.
WARNING: column type "character varying" used for "idata_value" does not follow best practices
HINT: Use datatype TEXT instead.
WARNING: column type "character varying" used for "raw_value" does not follow best practices
HINT: Use datatype TEXT instead.
WARNING: column type "character varying" used for "event_message" does not follow best practices
HINT: Use datatype TEXT instead.
WARNING: column type "character varying" used for "event_tags" does not follow best practices
HINT: Use datatype TEXT instead.
WARNING: column type "character varying" used for "notification_channel" does not follow best practices
HINT: Use datatype TEXT instead.
WARNING: column type "character varying" used for "recipient" does not follow best practices
HINT: Use datatype TEXT instead.
WARNING: column type "character varying" used for "subject" does not follow best practices
HINT: Use datatype TEXT instead.
WARNING: column type "character varying" used for "message" does not follow best practices
HINT: Use datatype TEXT instead.
WARNING: column type "character varying" used for "action_name" does not follow best practices
HINT: Use datatype TEXT instead.
WARNING: column type "character varying" used for "channel_name" does not follow best practices
HINT: Use datatype TEXT instead.
WARNING: column type "character varying" used for "recipient" does not follow best practices
HINT: Use datatype TEXT instead.
WARNING: column type "character varying" used for "subject" does not follow best practices
HINT: Use datatype TEXT instead.
WARNING: column type "character varying" used for "action_data" does not follow best practices
HINT: Use datatype TEXT instead.
WARNING: column type "character varying" used for "hostname" does not follow best practices
HINT: Use datatype TEXT instead.
WARNING: column type "character varying" used for "msg_tag" does not follow best practices
HINT: Use datatype TEXT instead.
WARNING: column type "character varying" used for "ip_addr" does not follow best practices
HINT: Use datatype TEXT instead.
WARNING: column type "character varying" used for "trap_oid" does not follow best practices
HINT: Use datatype TEXT instead.
WARNING: column type "character varying" used for "log_name" does not follow best practices
HINT: Use datatype TEXT instead.
WARNING: column type "character varying" used for "event_source" does not follow best practices
HINT: Use datatype TEXT instead.
WARNING: column type "character varying" used for "message" does not follow best practices
HINT: Use datatype TEXT instead.Everything initialized ok but just thought this was strange.
-
Which Postgres and Timescale versions do you use?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login