| From: | Matt Magoffin <postgresql(dot)org(at)msqr(dot)us> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Duplicate key violation on upsert |
| Date: | 2020-03-26 18:50:01 |
| Message-ID: | D2CDA6DF-5D6C-4B56-A51A-623D6016FE9A@msqr.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On 27/03/2020, at 5:26 AM, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
>
> Well morning and coffee helped some, but not enough to offer blinding insight. Reviewing the function above, the TimescaleDB insert block function and the overview of the TimescaleDB hypertable architecture leads me to believe there is some sort of conflict between the solarnetwork functions and the TimescaleDB hypertable actions. It is a wishy-washy answer as I do not understand the TimescaleDB architecture well enough. You might want to reach to the TimescaleDB community to see if they can offer any further insight.
Fair enough! Thank you for taking the time to look through this issue with me, I really appreciate it. I’ll reach out the the TimescaleDB folks and see what they think.
— m@
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ted To | 2020-03-26 19:29:33 | Ident authentication failed |
| Previous Message | David Gauthier | 2020-03-26 18:38:37 | Re: How can I recreate a view in a new schema such that the view def references tables in the new schema ? |