On 4/27/23 17:58, Michael Xu wrote:
Please reply to list also.
Ccing list.
1) Are you sure whatever client you are using is not doing
"ads.MyTableName"?
Confirm, it is not ads.MyTableName.
1) What client(and it's version) are you using?
2) What I asked was whether the schema and table nam
> On Apr 27, 2023, at 12:40 PM, Michael Xu wrote:
>
>
> Hi,
>
> By default, pgsql accepts double quotes around schema's name in a query, e.g.
> select * from "ads"."MyTableName". In our env, it throws 42P01:relation
> "ads.MyTableName" does not exist. It is okay if no double quote around s
On 4/27/23 12:40, Michael Xu wrote:
Hi,
By default, pgsql accepts double quotes around schema's name in a query,
e.g. select * from "ads"."MyTableName". In our env, it throws
42P01:relation "ads.MyTableName" does not exist. It is okay if no double
quote around schema name, select * from ads."
> On Apr 27, 2023, at 12:40, Michael Xu wrote:
> In our env, it throws 42P01:relation "ads.MyTableName" does not exist.
The function of double quotes in SQL is to allow you do include characters that
would otherwise not be legal in an identifier (as well as making the identifier
case-sensiti
Michael Xu writes:
> By default, pgsql accepts double quotes around schema's name in a query,
> e.g. select * from "ads"."MyTableName". In our env, it throws
> 42P01:relation "ads.MyTableName" does not exist.
Works for me:
regression=# create schema ads;
CREATE SCHEMA
regression=# create table "
Hi,
By default, pgsql accepts double quotes around schema's name in a query,
e.g. select * from "ads"."MyTableName". In our env, it throws
42P01:relation "ads.MyTableName" does not exist. It is okay if no double
quote around schema name, select * from ads."MyTableName".
Is there settings in pssql
On Fri, Mar 11, 2022 at 10:02:39AM +, Ian Dauncey wrote:
> Can anyone assist in shedding some light here.
> We getting this query popping up in our postgresql log file at the same time
> as the connections to the databases starts increasing.
> Not sure what is initiating this query, but we get
Hi All
Can anyone assist in shedding some light here.
We getting this query popping up in our postgresql log file at the same time as
the connections to the databases starts increasing.
Not sure what is initiating this query, but we get around a hundred per second
until we restart our applicati
