-functions/48190288?noredirect=1#comment83364017_48190288
is neither ideal nor efficient.
IMHO since combine functions accept parameters I don't see why final
functions should not also accept parameters.
--
----
Prof. Esteban Zimanyi
>
> So these are 4 different data types (or classes of data types) that you
> introduce in your extension? Or is that just a conceptual view and it's
> stored in some other way (e.g. normalized in some way)?
>
At the SQL level these 4 durations are not distinguishable. For example for
a tfloat
egards
Esteban
--
----
Prof. Esteban Zimanyi
Department of Computer & Decision Engineering (CoDE) CP 165/15
Universite Libre de Bruxelles
Avenue F. D. Roosevelt 50
B-1050 Brussels, Belgium
fax: + 32.2.650.47.13
tel: + 32.2.650.31.85
e-mail: ezima...@ulb.a
ban
--
Prof. Esteban Zimanyi
Department of Computer & Decision Engineering (CoDE) CP 165/15
Universite Libre de Bruxelles
Avenue F. D. Roosevelt 50
B-1050 Brussels, Belgium
fax: + 32.2.650.47.13
tel: + 32.2.650.31.85
e-mail: ezima...@ulb.ac.be
Internet: http://code.ulb.ac.be/
the implications of
these changes. Please let me know.
Esteban
On Thu, Sep 5, 2019 at 5:11 PM Tom Lane wrote:
> Esteban Zimanyi writes:
> > We are developing the analyze/selectivity functions for those types. Our
> > approach is to use the standard PostgreSQL/PostGIS functions
here a better way to do this ?
Is there any chance that the API for accessing the typanalyze and
selectivity functions will be enhanced in a future release ?
Regards
Esteban
--
--------
Prof. Esteban Zimanyi
Department of Computer & Decision
Dear all
While developing MobilityDB we needed to extend the range type operators so
they cope with elements. In the same way that currently the range types
support both
- @> contains range/element
- <@ element/range is contained by
we extended the left (<<), overleft (&<), right (>>), and
On Tue, Sep 17, 2019 at 5:18 AM David Fetter wrote:
> It's not done by pull request at this time. Instead, it is done by sending
> patches to this mailing list.
Dear all
You will find enclosed the patch that extends the range type operators so
they cope with elements.
Any comments most
Dear all
In MobilityDB
https://github.com/MobilityDB/MobilityDB
we use extensively the range types.
Is there any possibility to make the function range_union_internal available to
use by other extensions ? Otherwise we need to copy/paste it verbatim. For
example lines 114-153 in
Dear all
Since always I have used geometric types as a great pedagogical example in
order to understand how indexes work in PostgreSQL so that I can program
our indexes in MobilityDB
https://github.com/MobilityDB/MobilityDB
However, this requires to create tables with a big number of geometries.
Dear all
Is there a pedagogical example showing KNN processing in GiST indexes ? I
am looking for something equivalent to the example in file geo_spgist.c.
Thanks for your help
Esteban
Prof. Esteban Zimanyi
Department of Computer & Decision Engineering (CoDE) CP 165/15
Universite Libre de Bruxelles
Avenue F. D. Roosevelt 50
B-1050 Brussels, Belgium
fax: + 32.2.650.47.13
tel: + 32.2.650.31.85
e-mail: ezima...@ulb.ac.be
Inte
Dear all
In MobilityDB we have defined parallel aggregations with a combine
function, e.g.,
CREATE AGGREGATE extent(tbox) (
SFUNC = tbox_extent_transfn,
STYPE = tbox,
COMBINEFUNC = tbox_extent_combinefn,
PARALLEL = safe
);
We would like to trigger the combine functions in the coverage
Thanks a lot! It works!
On Tue, May 18, 2021 at 11:15 AM Bharath Rupireddy <
bharath.rupireddyforpostg...@gmail.com> wrote:
> On Tue, May 18, 2021 at 2:32 PM Esteban Zimanyi
> wrote:
> >
> > Dear all
> >
> > In MobilityDB we have defined parallel aggrega
31, 2021 at 3:49 PM Tom Lane wrote:
> Esteban Zimanyi writes:
> > Any idea how to disable the autovacuum during the regression and coverage
> > tests for the MobilityDB extension ?
>
> TBH, this seems like a pretty bad idea. If your extension doesn't
> behave sta
Dear all
Any idea how to disable the autovacuum during the regression and coverage
tests for the MobilityDB extension ?
I have tried
alter system set autovacuum = off;
but it does not seem to work.
Any suggestions are much appreciated.
Esteban
the tests
Thanks for your help !
On Mon, May 31, 2021 at 10:47 AM Christoph Moench-Tegeder <
c...@burggraben.net> wrote:
> ## Esteban Zimanyi (ezima...@ulb.ac.be):
>
> > I have tried
> > alter system set autovacuum = off;
> > but it does not seem to work.
>
&
Dear Tom
Many thanks for asking my question so quickly. After your answer, I
downloaded brand new versions of PostgreSQL 13.2, PostGIS 2.5.5, and
compiled/installed with the standard parameters. I didn't get any error
messages in the build. I then recompiled again MobilityDB and got the same
Dear all
Since I was receiving an error when defining a set returning function, I
borrowed a function from PostgreSQL as follows
/* C definition */
typedef struct testState
{
int current;
int finish;
int step;
} testState;
/**
* test_srf(startval int, endval int, step int)
*/
Many thanks Tom for your help !
I removed the flag -fshort-enums and everything works fine !
On Fri, Apr 16, 2021 at 7:04 PM Tom Lane wrote:
> Esteban Zimanyi writes:
> > When debugging the function with gdb, I noticed that the rsinfo variable
> of
> > the P
> If you build with pgxs it should supply the appropriate compiler flags.
> Alternatively, get the right settings from pg_config. In general rolling
> your own is a bad idea.
>
I didn't know about pgxs. Many thanks Andrew for pointing this out.
Hello
While executing the regression tests for MobilityDB I load a predefined
database on which I run the tests and then compare the results obtained
with those expected. All the tests are driven by the following bash file
https://github.com/MobilityDB/MobilityDB/blob/develop/test/scripts/test.sh
Windows 10 supports Unix sockets as reported, e.g., here
https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/
We run the tests on MobilityDB using an ephemeral instance that is created
by the test suite and torn down afterwards.
Dear all
May I kindly ask your insight about a question I posted 1 month ago and for
which I never received any answer ?
Many thanks
On Thu, Jan 6, 2022 at 4:05 PM Esteban Zimanyi
wrote:
> Dear all
>
> When ingesting mobility (IoT) data into MobilityDB
> https://mobilitydb.com/
&g
Many thanks for your prompt reply David. Allow me then to restate the
questions, hoping that this better fits this mailing list.
MobilityDB is a time-series extension to PostgreSQL/PostGIS in which
time-varying attributes (e.g., gear, GPS location of a car) are
semantically grouped into "units"
Dear David
There are two approaches for storing temporal information in a relational
database, explored since the 1980s following the work of Richard Snodgrass
http://www2.cs.arizona.edu/~rts/publications.html
tuple-timestamping vs attribute-timestamping. The SQL standard used the
Dear all
When ingesting mobility (IoT) data into MobilityDB
https://mobilitydb.com/
we transform very wide (2K attributes) car mobility data of high frequence
(every tenth of a second) from flat format (e.g. CSV) into MobilityDB
format in which there is a single record per trip and each of the
MobilityDB
https://github.com/MobilityDB/MobilityDB
is a PostgreSQL extension that depends on PosGIS.
Bradford Boyle who has been working on packaging MobilityDB
https://www.postgresql.org/message-id/capqrbe716d3gpd0jdbafab72elajrppg1luzvobelnbgl3r...@mail.gmail.com
highlighted the issue of which
Dear all
MobilityDB (https://github.com/MobilityDB/MobilityDB) defines at the C
level four template types: Set, Span, SpanSet, and Temporal. The type Set
is akin to PostgreSQL's ArrayType restricted to one dimension, but enforces
the constraint that sets do not have duplicates, the types Span and
29 matches
Mail list logo
