On Mon, 2023-07-24 at 18:54 -0700, Badri Subramaniam wrote:
> Is there a way to turn off auto commit using the C API?
No.
Yours,
Laurenz Albe
On Tue, 2023-07-25 at 11:11 +0800, gzh wrote:
> > I asked for EXPLAIN (ANALYZE, BUFFERS, SETTINGS) ...
> > Or do you have a version that is too old for SETTINGS?
> Sorry. Please refer to the following execution plan.
>
> [...]
> Settings: effective_cache_size = '1886088kB', jit = 'off', search_pat
Thank you for your reply.
>I think the whole query can just:
>select COUNT(ET_CD)
>from TBL_SHA
>WHERE TBL_SHA.MS_CD = 'MLD009' AND TBL_SHA.ETRYS = '0001';
This is related to the business logic.
>if many duplicates rows returned, then there is no point of evaluate
>something like {1 in (1,1
>I asked for EXPLAIN (ANALYZE, BUFFERS, SETTINGS) ...
>Or do you have a version that is too old for SETTINGS?
Sorry. Please refer to the following execution plan.
EXPLAIN (ANALYZE, BUFFERS, SETTINGS)
select COUNT(ET_CD)
from TBL_SHA
WHERE TBL_SHA.MS_CD = 'MLD009'
and TBL_SHA.ETRYS in
Hello
Is there a way to turn off auto commit using the C API?
Thanks
Hi Ken and Adrian,
Thanks for the useful suggestions!
We've investigated a bit more on the collations and we're almost certain it
is the RC:
For Debian 11.11:
user=# select 'a' > 'A'; ?column? -- f (1 row) user=# select 'a'
< 'A'; ?column? -- t (1 row)
For Alpine 11.19:
user
On Mon, 2023-07-24 at 17:54 +0800, gzh wrote:
> EXPLAIN (ANALYZE ON, VERBOSE ON, COSTS ON, BUFFERS ON)
I asked for EXPLAIN (ANALYZE, BUFFERS, SETTINGS) ...
Or do you have a version that is too old for SETTINGS?
One other idea: check if the index is INVALID (this will
be visible if you run "\d ta
On Mon, Jul 24, 2023 at 7:52 AM Ron wrote:
> On 7/24/23 09:09, Tom Lane wrote:
>
> > GRANT ALL ON SCHEMA public TO public;
>
> I'd have naively expected "GRANT ALL ON SCHEMA public TO public; " to be
> taken care of by "GRANT ALL PRIVILEGES ON DATABASE cbdevdb TO
> cbdevdbadmin;".
>
>
I'm quite h
On Mon, Jul 24, 2023 at 2:43 AM Wen Yi wrote:
> Hi community,
> I am learning the kernel of the postgres, and I want to test the
> make_relative_path function to know what it's operational principle.(I can
> read it's code, and I want to actually run it)
> But I really don't know how to do it, wr
On 7/24/23 09:09, Tom Lane wrote:
"David G. Johnston" writes:
The error message is misleading, you can’t directly create tables in a
database, you must create them in a schema and the permission to do so is
granted to the role on the schema, not the database.
The actual server message is going
On Mon, Jul 24, 2023 at 5:54 PM gzh wrote:
>
> >Did you change any parameters that have an impact on query planning?
>
> >You can see that in the output of EXPLAIN (ANALYZE, BUFFERS, SETTINGS).
>
> I added some parameters and re-executed the Execution Plan.
>
> Except for the index not taking effe
On 2023-Jul-24, Ron wrote:
> Add namespace_a and namespace_b to your search_path. Then it will work.
>
> Off the top of my head:
> SET search_path = namespace_a, namespace_b, public;
Actually it won't, because the table in the earliest schema "shadows"
any other tables of the same name in later
"David G. Johnston" writes:
> The error message is misleading, you can’t directly create tables in a
> database, you must create them in a schema and the permission to do so is
> granted to the role on the schema, not the database.
The actual server message is going to be just
ERROR: permission
On Monday, July 24, 2023, Kaushal Shriyan wrote:
>
>
> Are you sure the configured username has the necessary permissions to
> create tables in the database?
>
The error message is misleading, you can’t directly create tables in a
database, you must create them in a schema and the permission to
On 7/23/23 19:25, Wen Yi wrote:
Hi community,
here's my shell:
I think it should print the table on namespace_a & namespace_b, not just
public, it really confused me.
Can someone give me some advice?
Read about search_path:
https://www.postgresql.org/docs/current/ddl-schemas.html#DDL-SCHEM
On Mon, Jul 24, 2023 at 6:51 PM Ron wrote:
>
> On 7/24/23 08:15, Kaushal Shriyan wrote:
> > Hi,
> >
> > I am running postgresql15-server 15.3 on Red Hat Enterprise Linux
> > release 8.7 (Ootpa)
> >
> > # rpm -qa | grep -i post
> > postgresql15-server-15.3-2PGDG.rhel8.x86_64
> > postgresql15-libs-1
On 7/24/23 08:15, Kaushal Shriyan wrote:
Hi,
I am running postgresql15-server 15.3 on Red Hat Enterprise Linux
release 8.7 (Ootpa)
# rpm -qa | grep -i post
postgresql15-server-15.3-2PGDG.rhel8.x86_64
postgresql15-libs-15.3-2PGDG.rhel8.x86_64
postgresql15-15.3-2PGDG.rhel8.x86_64
#
$psql
psql (1
On 7/23/23 21:25, Wen Yi wrote:
Hi community,
here's my shell:
postgres=# \d
Did not find any relations.
postgres=# create schema namespace_a;
CREATE SCHEMA
postgres=# create schema namespace_b;
CREATE SCHEMA
postgres=# create table simple (name varchar);
CREATE TABLE
postgres=# create table nam
Hi,
I am running postgresql15-server 15.3 on Red Hat Enterprise Linux
release 8.7 (Ootpa)
# rpm -qa | grep -i post
postgresql15-server-15.3-2PGDG.rhel8.x86_64
postgresql15-libs-15.3-2PGDG.rhel8.x86_64
postgresql15-15.3-2PGDG.rhel8.x86_64
#
$psql
psql (15.3)
Type "help" for help.
postgres=# GRAN
On Fri, Jul 21, 2023 at 4:58 PM Tom Lane wrote:
> Joseph Koshakow writes:
> > Is this an intentional decision to not support a binary encoding for
> > aclitem types? Or is it just a lack of a feature?
>
I'm also using binary input/output, and for ACLs, when not using the usual
ACL related funct
>Did you change any parameters that have an impact on query planning?
>You can see that in the output of EXPLAIN (ANALYZE, BUFFERS, SETTINGS).
I added some parameters and re-executed the Execution Plan.
Except for the index not taking effect, I still don't know the reason why the
index is not w
Hi,
try: \d *.*
where: *.* = schema.table
Best regards / Cordialement / S pozdravem / S poštovanjem,
*Antonio Čale*
On Mon, Jul 24, 2023 at 11:43 AM Wen Yi wrote:
> Hi community,
> here's my shell:
>
> postgres=# \d
> Did not find any relations.
> postgres=# create schema namespace_a;
> CREAT
Hi community,
I am learning the kernel of the postgres, and I want to test the
make_relative_path function to know what it's operational principle.(I can read
it's code, and I want to actually run it)
But I really don't know how to do it, wrtite a extension?
Can someone give me some advice?
Tha
Hi community,
here's my shell:
postgres=# \d
Did not find any relations.
postgres=# create schema namespace_a;
CREATE SCHEMA
postgres=# create schema namespace_b;
CREATE SCHEMA
postgres=# create table simple (name varchar);
CREATE TABLE
postgres=# create table namespace_a.simple (name varchar);
24 matches
Mail list logo