[prev in list] [next in list] [prev in thread] [next in thread]
List: postgresql-general
Subject: Re: Duplicate key violation on upsert
From: Matt Magoffin <postgresql.org () msqr ! us>
Date: 2020-03-26 18:50:01
Message-ID: D2CDA6DF-5D6C-4B56-A51A-623D6016FE9A () msqr ! us
[Download RAW message or body]
> On 27/03/2020, at 5:26 AM, Adrian Klaver <adrian.klaver@aklaver.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@
[Attachment #3 (unknown)]
<html><head><meta http-equiv="Content-Type" content="text/html; \
charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; \
line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" \
class=""><div class="">On 27/03/2020, at 5:26 AM, Adrian Klaver <<a \
href="mailto:adrian.klaver@aklaver.com" class="">adrian.klaver@aklaver.com</a>> \
wrote:</div><br class="Apple-interchange-newline"><div class=""><span \
style="caret-color: rgb(0, 0, 0); font-family: Helvetica-Light; font-size: 13px; \
font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: \
normal; text-align: start; text-indent: 0px; text-transform: none; white-space: \
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; \
float: none; display: inline !important;" class="">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.</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica-Light; \
font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; \
letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; \
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; \
text-decoration: none;" class=""></div></blockquote></div><br class=""><div \
class="">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.</div><div class=""><br class=""></div><div class="">— \
m@</div></body></html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic