On 2/27/25 09:05, Achilleas Mantzios - cloud wrote:
On 2/26/25 18:29, Adrian Klaver wrote:
On 2/26/25 01:27, Achilleas Mantzios - cloud wrote:
Hi Again
Up to this day we have set the data acquisition system running for
just one ship and writing the code to display the data. For less
than
On 2/26/25 18:29, Adrian Klaver wrote:
On 2/26/25 01:27, Achilleas Mantzios - cloud wrote:
Hi Again
Up to this day we have set the data acquisition system running for
just one ship and writing the code to display the data. For less than
20 days we have 6M rows.
I gave a shot to timescale,
On 2/26/25 01:27, Achilleas Mantzios - cloud wrote:
Hi Again
Up to this day we have set the data acquisition system running for just
one ship and writing the code to display the data. For less than 20 days
we have 6M rows.
I gave a shot to timescale, installed locally as an extension, it see
Hi Again
Up to this day we have set the data acquisition system running for just
one ship and writing the code to display the data. For less than 20 days
we have 6M rows.
I gave a shot to timescale, installed locally as an extension, it seems
much prettier than having to do all the partition
On 2/13/25 20:44, Thiemo Kellner wrote:
13.02.2025 10:54:05 Achilleas Mantzios - cloud
:
If we followed a strict normalized approach then we would create additionally
11 tables each tag of type c) . And we are not guaranteed that the same tags
would have the same structure over the whole f
On 2/14/25 11:34, Allan Kamau wrote:
On Thu, Feb 13, 2025 at 9:44 PM Thiemo Kellner
wrote:
13.02.2025 10:54:05 Achilleas Mantzios - cloud
:
> If we followed a strict normalized approach then we would create
additionally 11 tables each tag of type c) . And we are not
gu
On 2/13/25 19:12, Adrian Klaver wrote:
On 2/13/25 01:53, Achilleas Mantzios - cloud wrote:
Now my problem is on the design . We have :
a) tags that have primitive values, float4 lets say - this is the
majority, e.g. 60% of all tags
b) tags that contain alarms data also with defined structu
On Thu, Feb 13, 2025 at 9:44 PM Thiemo Kellner
wrote:
> 13.02.2025 10:54:05 Achilleas Mantzios - cloud <
> a.mantz...@cloud.gatewaynet.com>:
>
> > If we followed a strict normalized approach then we would create
> additionally 11 tables each tag of type c) . And we are not guaranteed that
> the s
13.02.2025 10:54:05 Achilleas Mantzios - cloud
:
> If we followed a strict normalized approach then we would create additionally
> 11 tables each tag of type c) . And we are not guaranteed that the same tags
> would have the same structure over the whole fleet/manufacturers. So we are
> thinki
On 2/13/25 01:53, Achilleas Mantzios - cloud wrote:
Now my problem is on the design . We have :
a) tags that have primitive values, float4 lets say - this is the
majority, e.g. 60% of all tags
b) tags that contain alarms data also with defined structure, which have
additional data such as ti
On 1/30/25 18:45, Adrian Klaver wrote:
On 1/30/25 06:18, Achilleas Mantzios - cloud wrote:
Dear PostgreSQL people
We have a project having to do with capturing sensor data and alarms
from various machinery using various protocols/standards (e.g. NMEA ,
MODBUS). We have about 150 sites (vess
On 1/30/25 06:18, Achilleas Mantzios - cloud wrote:
Dear PostgreSQL people
We have a project having to do with capturing sensor data and alarms
from various machinery using various protocols/standards (e.g. NMEA ,
MODBUS). We have about 150 sites (vessels of various types) and each
site will
Dear PostgreSQL people
We have a project having to do with capturing sensor data and alarms
from various machinery using various protocols/standards (e.g. NMEA ,
MODBUS). We have about 150 sites (vessels of various types) and each
site will generate about 500 rows per minute. We have solved mo
13 matches
Mail list logo
