Hi,
This patch fixes a missing entry in the parser README. The file
parse_jsontable.c exists but wasn't documented in the README.
The patch adds the missing line with an appropriate description.
Please find the patch attached.
Best regards,
Karthik S
0001-Update-parser-README-to-in
nsistent error message in both
scenarios but it offers no real functional gains.
1. Is there a different reason the two queries produce a different error?
2. Is there a better way to think about the "command cannot affect row a
second time"? Appreciate any guidance. Thanks.
Warm regards,
Karthi
Thanks Justin for prompt response. Could you please provide the full email for
pgsql-user? pgsql-u...@postgresql.org<mailto:pgsql-u...@postgresql.org> is not
working
From: Justin Pryzby
Date: Tuesday, 15 November 2022 at 9:02 PM
To: Karthik Jagadish (kjagadis)
Cc: pgsql-hack...@postgres
ma||'.'||table_name))) as size from
information_schema.tables"
size
151 GB
(1 row)
$ sudo du -hsc /var/lib/pgsql/12/data
154G/var/lib/pgsql/12/data
154Gtotal
Appreciate if someone can give some pointers.
Regards,
Karthik
I didn’t get your point dead tuples are visible to transaction means? Vacuuming
job is to remove dead tuples right?
Regards,
Karthik
From: Amul Sul
Date: Tuesday, 8 November 2022 at 6:39 PM
To: Karthik Jagadish (kjagadis)
Cc: pgsql-hack...@postgresql.org , Prasanna
Satyanarayanan (prassaty
?
Regards,
Karthik
From: Amul Sul
Date: Tuesday, 8 November 2022 at 5:38 PM
To: Karthik Jagadish (kjagadis)
Cc: pgsql-hack...@postgresql.org , Prasanna
Satyanarayanan (prassaty) , Chandruganth Ayyavoo Selvam
(chaayyav) , Jaganbabu M (jmunusam)
Subject: Re: Tables not getting vacuumed in postgres
On
tables?
Autovacuum is enabled
Regards,
Karthik
gms [local]
VACUUM waiting
postgres 18437 62646 0 Jul27 ?00:00:00 postgres: postgres cgms [local]
VACUUM waiting
Regards,
Karthik
From: Julien Rouhaud
Date: Monday, 7 November 2022 at 7:06 PM
To: Laurenz Albe
Cc: Karthik Jagadish (kjagadis) , Dave Page
, pgsql-hack...@postgresql.org
, Ch
ause
some lock is present in the table/db or any other reason?
Regards,
Karthik
From: Dave Page
Date: Monday, 7 November 2022 at 5:17 PM
To: Karthik Jagadish (kjagadis)
Cc: pgsql-hack...@postgresql.org , Chandruganth
Ayyavoo Selvam (chaayyav) , Prasanna Satyanarayanan
(prassaty) , Jaganbabu M
that it’s showing as on
[Graphical user interface, timeline Description automatically generated]
What would this mean? Does it mean that autovacuum is not disabled? Appreciate
a response.
Regards,
Karthik
,
Srinivas Karthik
On Wed, Jul 4, 2018 at 10:27 PM, Peter Geoghegan wrote:
> On Tue, Jul 3, 2018 at 4:34 PM, Srinivas Karthik V
> wrote:
> > @Peter: I was indexing the primary key of all the tables in tpc-ds. Some
> of
> > the fact tables has multiple columns as part of the prim
@Peter: I was indexing the primary key of all the tables in tpc-ds. Some of
the fact tables has multiple columns as part of the primary key. Also, most
of them are numeric type.
On Mon, Jul 2, 2018 at 7:09 AM, Peter Geoghegan wrote:
> On Sun, Jul 1, 2018 at 5:19 PM, Tsunakawa, Takayuki
> wrote:
I was using copy command to load. Removing the primary key constraint on
the table and then loading it helps a lot. In fact, a 400GB table was
loaded and the primary constraint was added in around 15 hours. Thanks for
the wonderful suggestions.
Regards,
Srinivas Karthik
On 28 Jun 2018 2:07 a.m
ation. This is the only possible
index being created before data loading and I am sure there are no other
indexes apart from the primary key column(s).
Regards,
Srinivas Karthik
14 matches
Mail list logo
