Tag Info

New answers tagged

1

I use modules in two projects I have developed. With modules, I can organize the code more easily, and hide routines from the users. Also, modules provide me a way to have a standard name for the module, and the schema provide the version (https://www.ibm.com/developerworks/community/blogs/SQLTips4DB2LUW/entry/appupgrade?lang=en_us) ...


0

It may be that i was doing something wrong here since I am very new to postgres. But this only solved the first part of the problem for me - setting the privileges on all existing tables. In order for permissions to be correctly set for my user on new tables that are created i has to set default permissions for the user: ALTER DEFAULT PRIVILEGES IN SCHEMA ...


1

Your entities are based on hours, not days, so you should go with one row per hour, just like you did, not a full day in a row. I did not understand if when you say data between two timestamps, if timestamp refers to the "inserted" column, or if it refers to the date and times on the data file. If it is the latter one, then having a datetime column for your ...


2

What is the most costly thing for you? Prioritize. Usually the most costly thing is confusion of users. Ordinary users very rarely use a TNS name. They usually use the data through a dedicated application, and know just the name of application, like CRM. Power users connect to TNS names (think SQLdeveloper), but they also connect to the ordinary ...


2

I certainly wouldn't want to include the server name in the TNS alias. It would seem highly probably that this would change over time as databases move from one server to another and as organizations move to things like RAC where there would be multiple servers. Assuming that your service names are chosen meaningfully, I would expect that the service name ...


2

It very much depends on cardinalities. How many rows in old and new table? How many of those result in DELETE / UPDATE / INSERT? TRUNCATE is fastest Generally, if large parts of the table are changed, a TRUNCATE / INSERT from function is probably the fastest way. If done in the same transaction, Postgres does not need to write WAL (since we start from ...



Top 50 recent answers are included