On Fri, Jan 21, 2022 at 5:39 AM Matthias Apitz wrote:
>
> Hello,
>
> Does the PostgreSQL (11.4 or 13.1) record somewhere in system tables
> the creation of INDEXes (or other objects)?
>
>
13.1? Really?
Features are not point-release dependent so v11 or v13 suffices when trying
to figure out whet
On Sat, Jan 08, 2022 at 08:12:50AM -0800, Adrian Klaver wrote:
> On 1/8/22 05:21, Ali Koca wrote:
>> I can't understand functions in md5.h, these are seemingly little bit
>> weird. Such as:
>> /* Utilities common to all the MD5 implementations,
>> as of md5_common.c */
>> extern bool
On Fri, Jan 21, 2022 at 01:38:59PM +0100, Matthias Apitz wrote:
> Does the PostgreSQL (11.4 or 13.1) record somewhere in system tables
> the creation of INDEXes (or other objects)?
Hard to say what you are looking for with such a general question.
Would pg_index or pg_indexes be enough? There ar
On 1/21/22 10:49 AM, Tom Lane wrote:
Adrian Klaver writes:
src/bin/psql/command.c
/*
* Ideally we should treat the arguments as SQL identifiers. But for
* backwards compatibility with 7.2 and older pg_dump files, we have to
* take unquoted arguments verbatim (don't downcase them).
Adrian Klaver writes:
> src/bin/psql/command.c
> /*
>* Ideally we should treat the arguments as SQL identifiers. But for
>* backwards compatibility with 7.2 and older pg_dump files, we have to
>* take unquoted arguments verbatim (don't downcase them). For now,
>* double-quoted arg
On Fri, Jan 21, 2022 at 11:32 AM Alanoly Andrews
wrote:
> Thanks Adrian. I was aware of that.
>
> But...in the case of FT definition, the quotes are mandatory after
> column_name in options. And it is a single quote.
>
Using an unqualified "quote" is this kind of discussion should be avoided.
T
On 1/21/22 10:32 AM, Alanoly Andrews wrote:
Thanks Adrian. I was aware of that.
But...in the case of FT definition, the quotes are mandatory after column_name
in options. And it is a single quote.
The problem here may be is that the "create foreign table" statement accepts only lower
case aft
Alanoly Andrews writes:
> But...in the case of FT definition, the quotes are mandatory after
> column_name in options. And it is a single quote.
Right. That string literal is not case-folded, so it has to accurately
match the actual spelling of the remote column name. Anything else we
might do
In answering a question on SO I discovered this:
\l PRODUCTION
List of databases
Name| Owner | Encoding | Collate |Ctype| Access
privileges
+--+--+-+-+---
production | pos
Thanks Adrian. I was aware of that.
But...in the case of FT definition, the quotes are mandatory after column_name
in options. And it is a single quote.
The problem here may be is that the "create foreign table" statement accepts
only lower case after options. Remember that the double quotes fo
On 1/21/22 10:04 AM, Alanoly Andrews wrote:
Following up on my previous message, there was a related problem with FT
definitions for which I have a workaround. It seems that the new
column_name after "options" in an FT definition cannot be in upper case.
See below:
When I define a foreign table
pgAdmin, as the name implies, is really for *administering* Postgresql in a
GUI manner, *not* for visualizing GIS coordinates.
On 1/21/22 10:26 AM, Shaozhong SHI wrote:
It would be nice to be able to write lines of scripts to tell PgAdmin to
show some visualisation of geographical features.
R
Following up on my previous message, there was a related problem with FT
definitions for which I have a workaround. It seems that the new column_name
after "options" in an FT definition cannot be in upper case. See below:
When I define a foreign table like below, I get an error in the subsequent
Dominique Devienne writes:
> On Fri, Jan 21, 2022 at 5:47 PM Tom Lane wrote:
>> There is a notion of "custom plans" in which parameter values are
>> inserted as constants, precisely to allow simplifications based on
>> known constant values. But this particular case isn't implemented.
> Where c
On Fri, Jan 21, 2022 at 5:47 PM Tom Lane wrote:
>> Dominique Devienne writes:
> > Will the query planner be able to *peek* into the args, and turn `colN like
> > $N` into a no-op?
Thanks for the replies, David and Tom.
> No. It would not do that even if the pattern were constant '%';
> it doe
Thanks Tom, Guillaume and Adrian.
My mistake in reversing the order of name and newname in the definition.
After the switch, it works.
ButI'm investigating another environment where the definition appears to
have been correct and yet there is an error in select. Maybe I'll post again
later,
Alanoly Andrews writes:
> I see that the syntax for the creation of a foreign table allows you to use a
> column name in the FT that is different from the one in the base table. Such
> a "create foreign table" statement executes successfully and creates the FT.
> But when I query the FT, I get
On Fri, Jan 21, 2022 at 9:26 AM Shaozhong SHI
wrote:
> It would be nice to be able to write lines of scripts to tell PgAdmin to
> show some visualisation of geographical features.
>
I wasn't aware pgAdmin had a command line oriented interface. I thought it
was pure GUI. The only scripts you wr
Dominique Devienne writes:
> Will the query planner be able to *peek* into the args, and turn the
> `colN like $N`
> into a no-op?
No. It would not do that even if the pattern were constant '%';
it doesn't know that much about that particular function.
There is a notion of "custom plans" in whi
Hi,
Le ven. 21 janv. 2022 à 17:24, Alanoly Andrews a
écrit :
> Hello,
>
> I see that the syntax for the creation of a foreign table allows you to
> use a column name in the FT that is different from the one in the base
> table. Such a "create foreign table" statement executes successfully and
>
On Fri, Jan 21, 2022 at 9:36 AM Dominique Devienne
wrote:
>
> for the various cases of empty argN strings, or does the planner do
> *bind-peeking*, and thus a single prepared statement would do the job,
> and still have different plans used depending on the actual binds?
>
> I'm assuming PostgreS
Hi,
I just saw some code of ours that takes 4 strings are arguments,
and wants to do optional filtering on those, in a SELECT statement.
Something like:
```
void foo(string arg1, string arg2, ...) {
... = exec(
conn, "SELECT * from tab where col1 like $1 and col2 like $2 and ...",
On 1/21/22 08:24, Alanoly Andrews wrote:
Hello,
I see that the syntax for the creation of a foreign table allows you to
use a column name in the FT that is different from the one in the base
table. Such a "create foreign table" statement executes successfully and
creates the FT. But when I que
Any functional code to be tested to confirm?
Regards,
David
On Fri, 21 Jan 2022 at 15:55, Laurenz Albe wrote:
> On Fri, 2022-01-21 at 14:33 +, Duarte Carreira wrote:
> > If we just create the 2 foreign tables, one complete and one without id,
> > you can simply insert into the table withou
It would be nice to be able to write lines of scripts to tell PgAdmin to
show some visualisation of geographical features.
Regards,
David
On Fri, 21 Jan 2022 at 15:14, David G. Johnston
wrote:
> It is amazing how much one can learn by reading documentation. You are
> looking for a section tha
Hello,
I see that the syntax for the creation of a foreign table allows you to use a
column name in the FT that is different from the one in the base table. Such a
"create foreign table" statement executes successfully and creates the FT. But
when I query the FT, I get an error wrt to the colum
On Fri, 2022-01-21 at 14:33 +, Duarte Carreira wrote:
> If we just create the 2 foreign tables, one complete and one without id,
> you can simply insert into the table without id and it will work fine.
> To select and show data, you use the "complete" table that has the id column.
>
> No need
> On Jan 21, 2022, at 4:45 AM, Moen, Paul T. wrote:
>
> I am seeing the following errors in my PostgreSQL log files and wonder if
> this is a problem with EDB's installation.
Yes, missing the proj.db would certainly make proj unhappy. Search your system
first and see if the file is actuall
It is amazing how much one can learn by reading documentation. You are
looking for a section that describes how to view, and possibly edit, data
in pgAdmin4.
David J.
On Fri, Jan 21, 2022 at 5:52 AM Shaozhong SHI
wrote:
> I just wonder whether commands can be typed in PgAdmin to view geometri
Hmmm... I don't think a view or trigger are necessary.
If we just create the 2 foreign tables, one complete and one without id,
you can simply insert into the table without id and it will work fine.
To select and show data, you use the "complete" table that has the id
column.
No need for trigger
On Thu, 2022-01-20 at 17:00 +, Garfield Lewis wrote:
> I need the page and possibly row of the data location to be stored as an
> element
> of the new type. This is to simulate a structure from another database system.
As I said, that is impossible.
Again, describe with many, many words what
On Thu, 2022-01-20 at 15:59 +, Duarte Carreira wrote:
> I got here after encountering the same difficulty, although on a much more
> mundane scenario.
>
> I'm used to fdw on a read-only basis. I was just inserting a new record on a
> foreign table
> and got blocked... and after much searchin
I just wonder whether commands can be typed in PgAdmin to view geometries.
Regards,
David
I am seeing the following errors in my PostgreSQL log files and wonder if this
is a problem with EDB's installation.
proj_create: Cannot find proj.db
proj_create: no database context specified
proj_create: Cannot find proj.db
proj_create: no database context specified
proj_create: Cannot find pro
Forgot to include pgsql-general@lists.postgresql.org in the Cc...
Forwarded Message
Subject: Re: PgAdmin is struggling and can we configure it so that it
works better
Date: Fri, 21 Jan 2022 13:42:13 +0100
From: Tomas Pospisek
To: Shaozhong SHI
On 21.01.22 12:42, Shaozhong
Hello,
Does the PostgreSQL (11.4 or 13.1) record somewhere in system tables
the creation of INDEXes (or other objects)?
Thanks
matthias
--
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
August 13, 1961: Bet
haman...@t-online.de writes:
> I am using a query pretty often that looks like
> SELECT <> WHERE <> AND
> <>
>
> Is there a way (with sql or plpgsql) to convert that into
> SELECT myquery('<>')
I would solve that by creating a view like:
CREATE VIEW some_view_name AS
SELECT <> WHERE <>;
See
Thanks for your help!
I'm not going forward with the id generating scheme... I prefer to let the
bd do that work on its own. Sharding is way over my head.
For now I just created the 2 tables, one for inserting (without the id
column), another for everything else. It's awkward and prone to human er
Some time, PgAdmin freezes and its response is very slow.
Some time, it gives strange display of table content. Perhaps, it is
related to the fact that PgAdmin is struggling with the amount of data it
thinks that it has to display.
I just wonder whether we can configure PgAdmin so that it will w
Le ven. 21 janv. 2022 à 11:14, a écrit :
>
>
> Hi,
>
> I am using a query pretty often that looks like
> SELECT <> WHERE <> AND
> <>
>
> Is there a way (with sql or plpgsql) to convert that into
> SELECT myquery('<>')
>
> Kind regards
> Wolfgang Hamann
>
>
>
> Hello Wolfgang,
You can use a FUNC
Hi,
I am using a query pretty often that looks like
SELECT <> WHERE <> AND
<>
Is there a way (with sql or plpgsql) to convert that into
SELECT myquery('<>')
Kind regards
Wolfgang Hamann
41 matches
Mail list logo
