Good morning,
>> 1) You are asking Postgres to do what previously you said you did not
>> want it to do:
>>
>>
>> https://www.postgresql.org/message-id/CADep2PMJVpVu-ne42yYpqjzGHQ1cunvX92Oo6_hNLfgrj%2BMa_Q%40mail.gmail.com
>>
>> " You are looking for Postgres to
>> > follow its responses all the
Good evening,
Thanks for the response.
On Wed, Oct 31, 2018, 2:59 PM Adrian Klaver On 10/31/18 2:03 AM, GPT wrote:
> > Very good morning,
> >
> > Thanks very much for your direct, clear and enlightening response!
> >
> > As regards Q2, and any other dynamic be
Very good morning,
Thanks very much for your direct, clear and enlightening response!
As regards Q2, and any other dynamic behaviour/feature or whatever PG
includes or will include in the future and has to do with 3rd entities
(modules, or whatever) of which the behaviour is out of the PG
control
Good afternoon!
> ...
> Postgres did not behave in a 'poor' way, the extension just did not
> interpret the results correctly.
Eh! Eh! Adrian/Christoph one minute please because this is something
new (at least in the very clear way you formulate it now and I can
understand it easily)!
The statement
Very good morning!
If, in 2018 when the human structures are very close to reach the edge
of our universe, here on earth you are asking me (a simple end-user),
in order to run the following "complicated" and "sophisticated" SQL
statements:
INSERT INTO my_table(key, value, expiry) VALUES ('my_key'
rful week!
On 10/28/18, Christoph Moench-Tegeder wrote:
> ## GPT (gptmailingli...@gmail.com):
>
>> Why this incident has been observed when the statement is only within
>> a function with variable as input parameter and not when they run
>> directly with explicitly define
On 10/27/18, Adrian Klaver wrote:
> On 10/27/18 2:28 AM, GPT wrote:
> ...
> Postgres is going to do all sorts of things under the hood when you run
> a query, that is not going to change.
+ Ok. That's clear.
+
> The issue you had bubbled up to
> you the user because the
changes.
Anyway, this is too technical for me and even if you respond most
probably I am not gonna get it.
Tia
On 10/27/18, GPT wrote:
> On 10/26/18, Christoph Moench-Tegeder wrote:
>> ## GPT (gptmailingli...@gmail.com):
>>
>>...
>>
>> And the important thing is: th
On 10/26/18, Christoph Moench-Tegeder wrote:
> ## GPT (gptmailingli...@gmail.com):
>
>...
>
> And the important thing is: there is no guarantee that the same SQL
> statement will always execute with the same plan:
+ Yes but there should be guarantee that when the statem
to respond properly.
Tia
On 10/25/18, Christoph Moench-Tegeder wrote:
> ## GPT (gptmailingli...@gmail.com):
>
>> So, this kind of switch after a few goes is a normal behavior or
>> something unexpected which will change in future?
>
> It's expected, and even document
So, this kind of switch after a few goes is a normal behavior or
something unexpected which will change in future?
I am asking in order to have my mind on incidents with similar behavior.
Tia
On 10/25/18, Andres Freund wrote:
> Hi,
>
> On 2018-10-25 11:43:39 +0200, GPT wrote:
>&g
Hi,
I have faced an incident which, according to the developer, "The
problem seems to be that pgsql switches from a CONST sub-expression
into a FUNCEXPR after a few goes, ..."
Please have a look at the following two links which describe the problem:
https://github.com/nahanni/rw_redis_fdw/issues
Unfortunately, I had not installed the following package:
"postgresql-server-dev-11"
By the way, shouldn't a warning message appear while trying to run:
`PATH=/usr/lib/postgresql/11/bin:$PATH make USE_PGXS=1`
warning the user that some files are missing.
Tia
On 10/22/18, G
Hi,
Both PG versions 10.5 and 11 are installed.
I have been trying to compile extensions for PG11 by using:
PATH=/.../11/bin:PATH make USE_...
but unfortunately PG10 is always being used (the `make` output always
shows PG10 and refers to `pg_config`).
1) Does it have to do with pg_config?
2) H
ase I define my own nonstandard view.
Krgds
On 12/30/17, Tom Lane wrote:
> GPT writes:
>> I would like to add an extra boolean attribute to table columns,
>
> The contents of the information_schema views are specified by the SQL
> standard (ISO 9075). Since the entire point of h
ally in IT "art" sector.
So, adding an extra boolean column to "information_schema.columns" or
"pg_attribute" will cause any "fatal" problem in the present?
Krgds
On 12/30/17, PT wrote:
> On Sat, 30 Dec 2017 20:33:28 +0100
> GPT wrote:
>
>> Pleas
Please visit the following link:
https://stackoverflow.com/q/48028501/8895614
but thing may go further/deeper than it seems.
Krds
On 12/30/17, Karsten Hilbert wrote:
> On Sat, Dec 30, 2017 at 08:17:34PM +0100, GPT wrote:
>
>> I would like to add an extra boolean attribute to t
I would like to add an extra boolean attribute to table columns,
something like NULL. Unfortunately Pg does not support such a feature:
ADD ATTRIBUTE TYPE TO COLUMN
;
For example:
ADD ATTRIBUTE is_displayed TYPE boolean TO COLUMN world.human.feature;
so that I can write:
SELECT column_name F
18 matches
Mail list logo
