temporary tables ?

From: "Zlatko Matic" <zlatko(dot)matic1(at)sb(dot)t-com(dot)hr>
To: "Michael Fuhr" <mike(at)fuhr(dot)org>, "Kilian Hagemann" <hagemann1(at)egs(dot)uct(dot)ac(dot)za>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: temporary tables ?
Date: 2005-07-22 17:55:15
Message-ID: 004501c58ee6$85a20fa0$d58a1dc3@zlatkovyfkpgz6
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello.
I have some tables that are updated by several users in the same time and
are used in queries for reports. Those tables have rows that are actualy
copied from original tables that are not to be altered. There is a
procedure that inserts rows for every user when connects, along with his
username, so different users can't interfere with each other because every
user has his own copy of rows that he can update, and records are filtered
by current_user.
Well, it's my heritage from MS Access, before I moved to Postgres, because
there is no such thing as temporary table in Access...
Now, I'm wondering is there any true advantage to implement temporary tables
for each user, insted of one table with inserted rows with username for
every user ?
What would be advantage of temporary tables?
Would database grow less if I implement temporary tables (less need for
vacuum ?), in comparison to my current solution with true table with rows
for every user ?

Zlatko

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Sean Davis 2005-07-22 18:06:22 Re: temporary tables ?
Previous Message Steve Crawford 2005-07-22 17:44:49 DST and potential changes thereto