louis gonzales wrote:
> Actually, there will be creation of 2 new tables for each insert on
> 'primary' table, so for 10K records, we would have 20K tables. Those
> tables each will never grow more than a few records each.
>
> Is it better to have 1 monolithic table and have to search it, or small
> individual tables but many of them?
20k tables sounds insane. I am not sure why you wouldn't want just one
table. I mean, you are saying a *few* records, so you are talking what
100k records in a single table instead?
100k is nothing.
Joshua D. Drake
Joshua D. Drake
> Ron Johnson wrote:
>
> On 03/15/07 22:14, louis gonzales wrote:
>
>
>>>> Hello List,
>>>> I want to write a statement-level trigger - one that happens once per
>>>> statement - such that, immediately after an insert into a table(which
>>>> gets a unique integer value as an ID from a defined sequence, being the
>>>> primary key on the table), a new table is created with foreign key
>>>>
> ^^^^^^^^^^^^^^^^^^^^
>
>
>>>> constraint on that unique ID.
>>>>
>
> So if you insert 10,000 records into T, you then have 10,000 new tables?
>
>>
---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend
>>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
