| From: | Nico Williams <nico(at)cryptonector(dot)com> |
|---|---|
| To: | Khalil Khamlichi <khamlichi(dot)khalil(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: time series data |
| Date: | 2017-10-02 18:14:54 |
| Message-ID: | 20171002181453.GD15754@localhost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
You have these choices:
- turn events into INSERTs and UPDATES on a table that represents a
single call
You might have an events VIEW with INSTED OF insert/update triggers
so you can insert events as the interface for updating calls.
- store the events and have a VIEW on the events table that gives you
rows that summarize each call
- both: store the events and the summaries of the calls
You might have an events table with AFTER INSERT triggers to insert
or update the corresponding rows in the calls table.
Nico
--
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2017-10-02 22:36:30 | Re: pg_stat_tmp and pg_upgrade |
| Previous Message | Khalil Khamlichi | 2017-10-02 17:27:32 | Re: time series data |