> I want to have long term storage and access to individual telegrams
An IOT is not designed for that. It is used for control or delivery of data
to a server.
You could have a PostgreSQL-client in the IOT but an MQ might be better.
Long term storage also means backup and recovery and I don't thin
On Mon, Oct 12, 2020 at 12:17:04PM -0500, John the Scott wrote:
> I am still new to github protocol, so i was not sure
> if asking about longer term support of rum was appropriate for
> the github issues posting.
Most of the original developers of rum are registered on this mailing
list so there w
No, instead i posted the compile errors.
I am still new to github protocol, so i was not sure
if asking about longer term support of rum was appropriate for
the github issues posting.
the differences between pg12 and pg13 seem considerable.
our internal use of rum has been spectacularly successfu
On 2020-10-12 10:40:03 -0400, Tom Lane wrote:
> "Peter J. Holzer" writes:
> > In the GROUP BY clause I can use the alias year which was defined
> > earlier in SELECT.
>
> This is a pretty unfortunate legacy thing that we support because
> backwards compatibility (and because "GROUP BY 1" is so f
On Fri, 2020-10-09 at 09:25 -0700, Guyren Howe wrote:
> I can find no evidence it’s ever been discussed here and there’s no mention
> of it on the PG website.
>
> So: is anyone considering adding this feature?
I think it would be useful, but non-trivial to implement.
Yours,
Laurenz Albe
--
Cyb
"Peter J. Holzer" writes:
> In my mental model of how SQL works, the clauses of an SQL query (if
> present) are processed in a certain order:
> FROM
> WHERE
> SELECT
> GROUP BY
> HAVING
> ORDER BY
> LIMIT
The SELECT list is certainly done after GROUP BY/HAVING. Consi
In my mental model of how SQL works, the clauses of an SQL query (if
present) are processed in a certain order:
FROM
WHERE
SELECT
GROUP BY
HAVING
ORDER BY
LIMIT
and each processes the output of the previous one.
However, consider this:
hjp=> select * from employe
On 17/09/2020 15:06, Tom Lane wrote:
=?UTF-8?Q?=C3=98ystein_Kolsrud?= writes:
So my question is: When does a postgres process forked for a connection use
private memory instead of shared, and what can I do to avoid this?
The only significant long-term consumption of private memory is for
cac
