>
>
>
> Also, I'm not sure that many extensions would really benefit from custom
> utility command, as you can already do pretty much anything you want using
> SQL
> functions. For instance it would be nice for hypopg to be able to support
>
> CREATE HYPOTHETICAL INDEX ...
>
> rather than
>
> SELE
po 15. 3. 2021 v 18:54 odesílatel Julien Rouhaud
napsal:
> On Mon, Mar 15, 2021 at 06:41:36PM +0100, Pavel Stehule wrote:
> > po 15. 3. 2021 v 18:18 odesílatel Julien Rouhaud
> > napsal:
> >
> > > On Mon, Mar 15, 2021 at 06:05:52PM +0100, Pavel Stehule wrote:
> > > >
> > > > Possibility to work
On Mon, Mar 15, 2021 at 06:41:36PM +0100, Pavel Stehule wrote:
> po 15. 3. 2021 v 18:18 odesílatel Julien Rouhaud
> napsal:
>
> > On Mon, Mar 15, 2021 at 06:05:52PM +0100, Pavel Stehule wrote:
> > >
> > > Possibility to work with a parser is one main reason for forking
> > postgres.
> > > Lot of
po 15. 3. 2021 v 18:18 odesílatel Julien Rouhaud
napsal:
> On Mon, Mar 15, 2021 at 06:05:52PM +0100, Pavel Stehule wrote:
> >
> > Possibility to work with a parser is one main reason for forking
> postgres.
> > Lot of interestings projects fail on the cost of maintaining their own
> fork.
> >
> >
On Mon, Mar 15, 2021 at 06:05:52PM +0100, Pavel Stehule wrote:
>
> Possibility to work with a parser is one main reason for forking postgres.
> Lot of interestings projects fail on the cost of maintaining their own fork.
>
> Maybe a good enough possibility is the possibility to inject an own pars
> Also, I'm not sure that many extensions would really benefit from custom
> utility command, as you can already do pretty much anything you want using
> SQL
> functions. For instance it would be nice for hypopg to be able to support
>
> CREATE HYPOTHETICAL INDEX ...
>
> rather than
>
> SELECT hyp
On Mon, Mar 15, 2021 at 12:58 PM Joel Jacobson wrote:
> On Mon, Mar 15, 2021, at 16:48, Jim Mlodgenski wrote:
>
> The example I have is adding a CREATE JOB command that a scheduler may
> use.
>
>
> This CREATE JOB thing sounds interesting.
>
> Are you working on adding the ability to schedule SQL
On Mon, Mar 15, 2021 at 12:43 PM Julien Rouhaud wrote:
> On Mon, Mar 15, 2021 at 11:48:58AM -0400, Jim Mlodgenski wrote:
> >
> > Going deeper on this, I created another POC as an example. Yes, having a
> > hook at the top of the parser does mean an extension needs to copy the
> > existing grammar
On Mon, Mar 15, 2021, at 16:48, Jim Mlodgenski wrote:
> The example I have is adding a CREATE JOB command that a scheduler may use.
This CREATE JOB thing sounds interesting.
Are you working on adding the ability to schedule SQL-commands to run in the
background,
similar to cronjob and/or adding
On Mon, Mar 15, 2021 at 11:48:58AM -0400, Jim Mlodgenski wrote:
>
> Going deeper on this, I created another POC as an example. Yes, having a
> hook at the top of the parser does mean an extension needs to copy the
> existing grammar and modify it. Without a total redesign of how the grammar
> is h
On Mon, Feb 22, 2021 at 3:52 PM Andres Freund wrote:
> Hi,
>
> On 2021-02-22 11:20:54 -0500, Jim Mlodgenski wrote:
> > As Jan mentioned in his thread about a pluggable wire protocol [0], AWS
> is
> > working on a set of extensions for Babelfish. The intention is to not
> > necessarily have it as
Hi,
On 2021-02-22 11:20:54 -0500, Jim Mlodgenski wrote:
> As Jan mentioned in his thread about a pluggable wire protocol [0], AWS is
> working on a set of extensions for Babelfish. The intention is to not
> necessarily have it as a single monolithic extension, but be possible for
> people to use p
12 matches
Mail list logo
