From: | Luca Ferrari <fluca1978(at)infinito(dot)it> |
---|---|
To: | Romain Billon-Grand <billongrand(at)hotmail(dot)fr> |
Cc: | felipepts(at)gmail(dot)com, akretschmer(at)spamfence(dot)net, "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: Keeping track of updates/performances |
Date: | 2015-03-18 07:40:31 |
Message-ID: | CAKoxK+7RaB3st-AgLKOJboHRA0aRiGgSJ7pPkq06a8x0omVnrg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On Tue, Mar 17, 2015 at 7:21 PM, Romain Billon-Grand
<billongrand(at)hotmail(dot)fr> wrote:
> ´now'::timestamp why not ´simply' current_timestamp?
>
That's the same (in the final run), the former uses a cast, the second
an internal variable.
Use current_ for anything you need.
> I have red about inheritance vs Like, but I wanted to know if one of those
> would have better performance
That's the wrong question, since it depends on what you are going to achieve.
Let's say that, being inheritance a way of tiying tables together, I
would expect to be able to have better performances in using like
tables, since I can tune them separately to exactly the need I have.
But again, it depends on what you are going to do with such tables and
what performances means to you (usage, creation, deletion, ...).
Luca
From | Date | Subject | |
---|---|---|---|
Next Message | Ravi Kiran | 2015-03-27 09:44:17 | Implementing a join algorithm in Postgres |
Previous Message | Luca Ferrari | 2015-03-18 07:37:30 | Re: [GENERAL] psql sqlstate return code access |