From: Tom Lane <tgl@sss.pgh.pa.us>
To: Borys K <koktos632@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16437: The dump is stored with error in creating VIEW statement.
Date: Thu, 14 May 2020 15:23:23 -0400
Message-ID: <12581.1589484203@sss.pgh.pa.us> (raw)
In-Reply-To: <CAOqhF_yRYtm3_VFd0KV-1cu4GAZp=7tWx60vr3Huw2cNx16FZQ@mail.gmail.com>
References: <16437-5257db04508943ab@postgresql.org>
<6545.1589476731@sss.pgh.pa.us>
<CAOqhF_zQfwTUDqSxmsN5wAunp3jbvrYxBzEK1ZAdqWdiA9fGSg@mail.gmail.com>
<CAOqhF_yRYtm3_VFd0KV-1cu4GAZp=7tWx60vr3Huw2cNx16FZQ@mail.gmail.com>
[ thanks for sending the off-list dump ]
Borys K <koktos632@gmail.com> writes:
> It is not a pure PostgreSQL server.
> I am using https://www.timescale.com/
Well, you'd really need to take this up with them. This view
seems to be using TimeScale-specific features, and I can't
even tell whether it ought to be legal. The view would certainly
not be legal in regular Postgres, because the table it's selecting
from has no unique indexes at all, so there's no basis for allowing
an abbreviated GROUP BY.
I'm suspecting that TimeScale may have special provisions for
dumping databases, because it's hard to see how this dump could
be reloaded as-is. But I don't know much about that product.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, koktos632@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16437: The dump is stored with error in creating VIEW statement.
In-Reply-To: <12581.1589484203@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox