agora inbox for [email protected]
help / color / mirror / Atom feed[PATCH v46 7/7] Exclude pg_stat directory from base backup
12+ messages / 7 participants
[nested] [flat]
* [PATCH v46 7/7] Exclude pg_stat directory from base backup
@ 2020-09-29 14:19 Kyotaro Horiguchi <[email protected]>
0 siblings, 0 replies; 12+ messages in thread
From: Kyotaro Horiguchi @ 2020-09-29 14:19 UTC (permalink / raw)
basebackup sends the content of pg_stat directory, which is doomed to
be removed at startup from the backup. Now that pg_stat_statements
saves a temporary file into the directory, let exclude pg_stat
directory from a base backup.
---
src/backend/replication/basebackup.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/src/backend/replication/basebackup.c b/src/backend/replication/basebackup.c
index d2c3064678..25677c5c6e 100644
--- a/src/backend/replication/basebackup.c
+++ b/src/backend/replication/basebackup.c
@@ -149,6 +149,13 @@ struct exclude_list_item
*/
static const char *const excludeDirContents[] =
{
+ /*
+ * Skip statistics files. PGSTAT_STAT_PERMANENT_DIRECTORY must be skipped
+ * because the files in the directory will be removed at startup from the
+ * backup.
+ */
+ PGSTAT_STAT_PERMANENT_DIRECTORY,
+
/*
* It is generally not useful to backup the contents of this directory
* even if the intention is to restore to another primary. See backup.sgml
--
2.27.0
----Next_Part(Thu_Jan_14_15_14_25_2021_903)----
^ permalink raw reply [nested|flat] 12+ messages in thread
* Fix error message for MERGE foreign tables
@ 2022-10-14 02:59 bt22nakamorit <[email protected]>
2022-10-14 04:07 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
0 siblings, 1 reply; 12+ messages in thread
From: bt22nakamorit @ 2022-10-14 02:59 UTC (permalink / raw)
To: PostgreSQL Hackers <[email protected]>
Hi,
MERGE command does not accept foreign tables as targets.
When a foreign table is specified as a target, it shows error messages
like this:
-- ERROR: cannot execute MERGE on relation "child1"
-- DETAIL: This operation is not supported for foreign tables.
However, when a partitioned table includes foreign tables as partitions
and MERGE is executed on the partitioned table, following error message
shows.
-- ERROR: unexpected operation: 5
The latter error message is unclear, and should be the same as the
former one.
The attached patch adds the code to display error the former error
messages in the latter case.
Any thoughts?
Best,
Tatsuhiro Nakamori
Attachments:
[text/x-diff] fdw_errmsg.patch (510B, ../../[email protected]/2-fdw_errmsg.patch)
download | inline diff:
diff --git a/contrib/postgres_fdw/postgres_fdw.c b/contrib/postgres_fdw/postgres_fdw.c
index d98709e5e8..b4fd54d913 100644
--- a/contrib/postgres_fdw/postgres_fdw.c
+++ b/contrib/postgres_fdw/postgres_fdw.c
@@ -1872,6 +1872,9 @@ postgresPlanForeignModify(PlannerInfo *root,
returningList,
&retrieved_attrs);
break;
+ case CMD_MERGE:
+ elog(ERROR, "MERGE not permitted on foreign tables");
+ break;
default:
elog(ERROR, "unexpected operation: %d", (int) operation);
break;
^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: Fix error message for MERGE foreign tables
2022-10-14 02:59 Fix error message for MERGE foreign tables bt22nakamorit <[email protected]>
@ 2022-10-14 04:07 ` Richard Guo <[email protected]>
2022-10-14 04:26 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
0 siblings, 1 reply; 12+ messages in thread
From: Richard Guo @ 2022-10-14 04:07 UTC (permalink / raw)
To: bt22nakamorit <[email protected]>; +Cc: PostgreSQL Hackers <[email protected]>
On Fri, Oct 14, 2022 at 10:59 AM bt22nakamorit <
[email protected]> wrote:
> Hi,
>
> MERGE command does not accept foreign tables as targets.
> When a foreign table is specified as a target, it shows error messages
> like this:
>
> -- ERROR: cannot execute MERGE on relation "child1"
> -- DETAIL: This operation is not supported for foreign tables.
>
> However, when a partitioned table includes foreign tables as partitions
> and MERGE is executed on the partitioned table, following error message
> shows.
>
> -- ERROR: unexpected operation: 5
>
> The latter error message is unclear, and should be the same as the
> former one.
> The attached patch adds the code to display error the former error
> messages in the latter case.
> Any thoughts?
+1. The new message is an improvement to the default one.
I wonder if we can provide more details in the error message, such as
foreign table name.
Thanks
Richard
^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: Fix error message for MERGE foreign tables
2022-10-14 02:59 Fix error message for MERGE foreign tables bt22nakamorit <[email protected]>
2022-10-14 04:07 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
@ 2022-10-14 04:26 ` Richard Guo <[email protected]>
2022-10-14 08:35 ` Re: Fix error message for MERGE foreign tables Michael Paquier <[email protected]>
0 siblings, 1 reply; 12+ messages in thread
From: Richard Guo @ 2022-10-14 04:26 UTC (permalink / raw)
To: bt22nakamorit <[email protected]>; +Cc: PostgreSQL Hackers <[email protected]>
On Fri, Oct 14, 2022 at 12:07 PM Richard Guo <[email protected]> wrote:
>
> On Fri, Oct 14, 2022 at 10:59 AM bt22nakamorit <
> [email protected]> wrote:
>
>> Hi,
>>
>> MERGE command does not accept foreign tables as targets.
>> When a foreign table is specified as a target, it shows error messages
>> like this:
>>
>> -- ERROR: cannot execute MERGE on relation "child1"
>> -- DETAIL: This operation is not supported for foreign tables.
>>
>> However, when a partitioned table includes foreign tables as partitions
>> and MERGE is executed on the partitioned table, following error message
>> shows.
>>
>> -- ERROR: unexpected operation: 5
>>
>> The latter error message is unclear, and should be the same as the
>> former one.
>> The attached patch adds the code to display error the former error
>> messages in the latter case.
>> Any thoughts?
>
>
> +1. The new message is an improvement to the default one.
>
> I wonder if we can provide more details in the error message, such as
> foreign table name.
>
Maybe something like below, so that we keep it consistent with the case
of a foreign table being specified as a target.
--- a/contrib/postgres_fdw/postgres_fdw.c
+++ b/contrib/postgres_fdw/postgres_fdw.c
@@ -1872,6 +1872,13 @@ postgresPlanForeignModify(PlannerInfo *root,
returningList,
&retrieved_attrs);
break;
+ case CMD_MERGE:
+ ereport(ERROR,
+ (errcode(ERRCODE_FEATURE_NOT_SUPPORTED),
+ errmsg("cannot execute MERGE on relation \"%s\"",
+ RelationGetRelationName(rel)),
+
errdetail_relkind_not_supported(rel->rd_rel->relkind)));
+ break;
Thanks
Richard
^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: Fix error message for MERGE foreign tables
2022-10-14 02:59 Fix error message for MERGE foreign tables bt22nakamorit <[email protected]>
2022-10-14 04:07 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
2022-10-14 04:26 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
@ 2022-10-14 08:35 ` Michael Paquier <[email protected]>
2022-10-14 08:47 ` Re: Fix error message for MERGE foreign tables Alvaro Herrera <[email protected]>
0 siblings, 1 reply; 12+ messages in thread
From: Michael Paquier @ 2022-10-14 08:35 UTC (permalink / raw)
To: Richard Guo <[email protected]>; +Cc: bt22nakamorit <[email protected]>; PostgreSQL Hackers <[email protected]>
On Fri, Oct 14, 2022 at 12:26:19PM +0800, Richard Guo wrote:
> Maybe something like below, so that we keep it consistent with the case
> of a foreign table being specified as a target.
>
> --- a/contrib/postgres_fdw/postgres_fdw.c
> +++ b/contrib/postgres_fdw/postgres_fdw.c
> @@ -1872,6 +1872,13 @@ postgresPlanForeignModify(PlannerInfo *root,
> returningList,
> &retrieved_attrs);
> break;
> + case CMD_MERGE:
> + ereport(ERROR,
> + (errcode(ERRCODE_FEATURE_NOT_SUPPORTED),
> + errmsg("cannot execute MERGE on relation \"%s\"",
> + RelationGetRelationName(rel)),
> +
> errdetail_relkind_not_supported(rel->rd_rel->relkind)));
> + break;
Yeah, you should not use an elog(ERROR) for cases that would be faced
directly by users.
--
Michael
Attachments:
[application/pgp-signature] signature.asc (833B, ../../[email protected]/2-signature.asc)
download
^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: Fix error message for MERGE foreign tables
2022-10-14 02:59 Fix error message for MERGE foreign tables bt22nakamorit <[email protected]>
2022-10-14 04:07 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
2022-10-14 04:26 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
2022-10-14 08:35 ` Re: Fix error message for MERGE foreign tables Michael Paquier <[email protected]>
@ 2022-10-14 08:47 ` Alvaro Herrera <[email protected]>
2022-10-14 09:24 ` Re: Fix error message for MERGE foreign tables Alvaro Herrera <[email protected]>
0 siblings, 1 reply; 12+ messages in thread
From: Alvaro Herrera @ 2022-10-14 08:47 UTC (permalink / raw)
To: Michael Paquier <[email protected]>; +Cc: Richard Guo <[email protected]>; bt22nakamorit <[email protected]>; PostgreSQL Hackers <[email protected]>
On 2022-Oct-14, Michael Paquier wrote:
> On Fri, Oct 14, 2022 at 12:26:19PM +0800, Richard Guo wrote:
> > Maybe something like below, so that we keep it consistent with the case
> > of a foreign table being specified as a target.
> >
> > --- a/contrib/postgres_fdw/postgres_fdw.c
> > +++ b/contrib/postgres_fdw/postgres_fdw.c
> > @@ -1872,6 +1872,13 @@ postgresPlanForeignModify(PlannerInfo *root,
> > returningList,
> > &retrieved_attrs);
> > break;
> > + case CMD_MERGE:
> > + ereport(ERROR,
> > + (errcode(ERRCODE_FEATURE_NOT_SUPPORTED),
> > + errmsg("cannot execute MERGE on relation \"%s\"",
> > + RelationGetRelationName(rel)),
> > +
> > errdetail_relkind_not_supported(rel->rd_rel->relkind)));
> > + break;
>
> Yeah, you should not use an elog(ERROR) for cases that would be faced
> directly by users.
Yeah, I think this just flies undetected until it hits code that doesn't
support the case. I'll add a test and push as Richard suggests, thanks.
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"La libertad es como el dinero; el que no la sabe emplear la pierde" (Alvarez)
^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: Fix error message for MERGE foreign tables
2022-10-14 02:59 Fix error message for MERGE foreign tables bt22nakamorit <[email protected]>
2022-10-14 04:07 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
2022-10-14 04:26 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
2022-10-14 08:35 ` Re: Fix error message for MERGE foreign tables Michael Paquier <[email protected]>
2022-10-14 08:47 ` Re: Fix error message for MERGE foreign tables Alvaro Herrera <[email protected]>
@ 2022-10-14 09:24 ` Alvaro Herrera <[email protected]>
2022-10-14 11:19 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
0 siblings, 1 reply; 12+ messages in thread
From: Alvaro Herrera @ 2022-10-14 09:24 UTC (permalink / raw)
To: Michael Paquier <[email protected]>; +Cc: Richard Guo <[email protected]>; bt22nakamorit <[email protected]>; PostgreSQL Hackers <[email protected]>
Actually, I hadn't realized that the originally submitted patch had the
test in postgres_fdw only, but we really want it to catch any FDW, so it
needs to be somewhere more general. The best place I found to put this
test is in make_modifytable ... I searched for some earlier place in the
planner to do it, but couldn't find anything.
So what do people think about this?
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"La grandeza es una experiencia transitoria. Nunca es consistente.
Depende en gran parte de la imaginación humana creadora de mitos"
(Irulan)
^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: Fix error message for MERGE foreign tables
2022-10-14 02:59 Fix error message for MERGE foreign tables bt22nakamorit <[email protected]>
2022-10-14 04:07 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
2022-10-14 04:26 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
2022-10-14 08:35 ` Re: Fix error message for MERGE foreign tables Michael Paquier <[email protected]>
2022-10-14 08:47 ` Re: Fix error message for MERGE foreign tables Alvaro Herrera <[email protected]>
2022-10-14 09:24 ` Re: Fix error message for MERGE foreign tables Alvaro Herrera <[email protected]>
@ 2022-10-14 11:19 ` Richard Guo <[email protected]>
2022-10-14 13:07 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
0 siblings, 1 reply; 12+ messages in thread
From: Richard Guo @ 2022-10-14 11:19 UTC (permalink / raw)
To: Alvaro Herrera <[email protected]>; +Cc: Michael Paquier <[email protected]>; bt22nakamorit <[email protected]>; PostgreSQL Hackers <[email protected]>
On Fri, Oct 14, 2022 at 5:24 PM Alvaro Herrera <[email protected]>
wrote:
> Actually, I hadn't realized that the originally submitted patch had the
> test in postgres_fdw only, but we really want it to catch any FDW, so it
> needs to be somewhere more general. The best place I found to put this
> test is in make_modifytable ... I searched for some earlier place in the
> planner to do it, but couldn't find anything.
>
> So what do people think about this?
Good point. I agree that the test should be in a more general place.
I wonder if we can make it earlier in grouping_planner() just before we
add ModifyTablePath.
--- a/src/backend/optimizer/plan/planner.c
+++ b/src/backend/optimizer/plan/planner.c
@@ -1772,6 +1772,17 @@ grouping_planner(PlannerInfo *root, double
tuple_fraction)
/* Build per-target-rel lists needed by ModifyTable */
resultRelations = lappend_int(resultRelations,
resultRelation);
+ if (parse->commandType == CMD_MERGE &&
+ this_result_rel->fdwroutine != NULL)
+ {
+ RangeTblEntry *rte = root->simple_rte_array[resultRelation];
+
+ ereport(ERROR,
+ errcode(ERRCODE_FEATURE_NOT_SUPPORTED),
+ errmsg("cannot execute MERGE on relation \"%s\"",
+ get_rel_name(rte->relid)),
+ errdetail_relkind_not_supported(rte->relkind));
+ }
Thanks
Richard
^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: Fix error message for MERGE foreign tables
2022-10-14 02:59 Fix error message for MERGE foreign tables bt22nakamorit <[email protected]>
2022-10-14 04:07 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
2022-10-14 04:26 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
2022-10-14 08:35 ` Re: Fix error message for MERGE foreign tables Michael Paquier <[email protected]>
2022-10-14 08:47 ` Re: Fix error message for MERGE foreign tables Alvaro Herrera <[email protected]>
2022-10-14 09:24 ` Re: Fix error message for MERGE foreign tables Alvaro Herrera <[email protected]>
2022-10-14 11:19 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
@ 2022-10-14 13:07 ` Richard Guo <[email protected]>
2022-10-14 14:43 ` Re: Fix error message for MERGE foreign tables Tom Lane <[email protected]>
0 siblings, 1 reply; 12+ messages in thread
From: Richard Guo @ 2022-10-14 13:07 UTC (permalink / raw)
To: Alvaro Herrera <[email protected]>; +Cc: Michael Paquier <[email protected]>; bt22nakamorit <[email protected]>; PostgreSQL Hackers <[email protected]>
On Fri, Oct 14, 2022 at 7:19 PM Richard Guo <[email protected]> wrote:
>
> On Fri, Oct 14, 2022 at 5:24 PM Alvaro Herrera <[email protected]>
> wrote:
>
>> Actually, I hadn't realized that the originally submitted patch had the
>> test in postgres_fdw only, but we really want it to catch any FDW, so it
>> needs to be somewhere more general. The best place I found to put this
>> test is in make_modifytable ... I searched for some earlier place in the
>> planner to do it, but couldn't find anything.
>>
>> So what do people think about this?
>
>
> Good point. I agree that the test should be in a more general place.
>
> I wonder if we can make it earlier in grouping_planner() just before we
> add ModifyTablePath.
>
Or maybe we can make it even earlier, when we expand an RTE for a
partitioned table and add result tables to leaf_result_relids.
--- a/src/backend/optimizer/util/inherit.c
+++ b/src/backend/optimizer/util/inherit.c
@@ -627,6 +627,16 @@ expand_single_inheritance_child(PlannerInfo *root,
RangeTblEntry *parentrte,
root->leaf_result_relids = bms_add_member(root->leaf_result_relids,
childRTindex);
+ if (parse->commandType == CMD_MERGE &&
+ childrte->relkind == RELKIND_FOREIGN_TABLE)
+ {
+ ereport(ERROR,
+ (errcode(ERRCODE_FEATURE_NOT_SUPPORTED),
+ errmsg("cannot execute MERGE on relation \"%s\"",
+ RelationGetRelationName(childrel)),
+ errdetail_relkind_not_supported(childrte->relkind)));
+ }
Thanks
Richard
^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: Fix error message for MERGE foreign tables
2022-10-14 02:59 Fix error message for MERGE foreign tables bt22nakamorit <[email protected]>
2022-10-14 04:07 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
2022-10-14 04:26 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
2022-10-14 08:35 ` Re: Fix error message for MERGE foreign tables Michael Paquier <[email protected]>
2022-10-14 08:47 ` Re: Fix error message for MERGE foreign tables Alvaro Herrera <[email protected]>
2022-10-14 09:24 ` Re: Fix error message for MERGE foreign tables Alvaro Herrera <[email protected]>
2022-10-14 11:19 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
2022-10-14 13:07 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
@ 2022-10-14 14:43 ` Tom Lane <[email protected]>
2022-10-17 02:07 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
0 siblings, 1 reply; 12+ messages in thread
From: Tom Lane @ 2022-10-14 14:43 UTC (permalink / raw)
To: Richard Guo <[email protected]>; +Cc: Alvaro Herrera <[email protected]>; Michael Paquier <[email protected]>; bt22nakamorit <[email protected]>; PostgreSQL Hackers <[email protected]>
Richard Guo <[email protected]> writes:
> Or maybe we can make it even earlier, when we expand an RTE for a
> partitioned table and add result tables to leaf_result_relids.
I'm not really on board with injecting command-type-specific logic into
completely unrelated places just so that we can throw an error a bit
earlier. Alvaro's suggestion of make_modifytable seemed plausible,
not least because it avoids spending any effort when the command
couldn't be MERGE at all.
regards, tom lane
^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: Fix error message for MERGE foreign tables
2022-10-14 02:59 Fix error message for MERGE foreign tables bt22nakamorit <[email protected]>
2022-10-14 04:07 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
2022-10-14 04:26 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
2022-10-14 08:35 ` Re: Fix error message for MERGE foreign tables Michael Paquier <[email protected]>
2022-10-14 08:47 ` Re: Fix error message for MERGE foreign tables Alvaro Herrera <[email protected]>
2022-10-14 09:24 ` Re: Fix error message for MERGE foreign tables Alvaro Herrera <[email protected]>
2022-10-14 11:19 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
2022-10-14 13:07 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
2022-10-14 14:43 ` Re: Fix error message for MERGE foreign tables Tom Lane <[email protected]>
@ 2022-10-17 02:07 ` Richard Guo <[email protected]>
0 siblings, 0 replies; 12+ messages in thread
From: Richard Guo @ 2022-10-17 02:07 UTC (permalink / raw)
To: Tom Lane <[email protected]>; +Cc: Alvaro Herrera <[email protected]>; Michael Paquier <[email protected]>; bt22nakamorit <[email protected]>; PostgreSQL Hackers <[email protected]>
On Fri, Oct 14, 2022 at 10:43 PM Tom Lane <[email protected]> wrote:
> Richard Guo <[email protected]> writes:
> > Or maybe we can make it even earlier, when we expand an RTE for a
> > partitioned table and add result tables to leaf_result_relids.
>
> I'm not really on board with injecting command-type-specific logic into
> completely unrelated places just so that we can throw an error a bit
> earlier. Alvaro's suggestion of make_modifytable seemed plausible,
> not least because it avoids spending any effort when the command
> couldn't be MERGE at all.
Yeah, that makes sense. Putting this check in inherit.c does look some
weird as there is no other commandType related code in that file.
Agree that Alvaro's suggestion is more reasonable.
Thanks
Richard
^ permalink raw reply [nested|flat] 12+ messages in thread
* [PATCH v8 7/7] Allow to print raw parse tree.
@ 2023-09-25 05:01 Tatsuo Ishii <[email protected]>
0 siblings, 0 replies; 12+ messages in thread
From: Tatsuo Ishii @ 2023-09-25 05:01 UTC (permalink / raw)
---
src/backend/tcop/postgres.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/backend/tcop/postgres.c b/src/backend/tcop/postgres.c
index 21b9763183..3e3653816e 100644
--- a/src/backend/tcop/postgres.c
+++ b/src/backend/tcop/postgres.c
@@ -651,6 +651,10 @@ pg_parse_query(const char *query_string)
}
#endif
+ if (Debug_print_parse)
+ elog_node_display(LOG, "raw parse tree", raw_parsetree_list,
+ Debug_pretty_print);
+
TRACE_POSTGRESQL_QUERY_PARSE_DONE(query_string);
return raw_parsetree_list;
--
2.25.1
----Next_Part(Mon_Sep_25_14_26_30_2023_752)----
^ permalink raw reply [nested|flat] 12+ messages in thread
end of thread, other threads:[~2023-09-25 05:01 UTC | newest]
Thread overview: 12+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2020-09-29 14:19 [PATCH v46 7/7] Exclude pg_stat directory from base backup Kyotaro Horiguchi <[email protected]>
2022-10-14 02:59 Fix error message for MERGE foreign tables bt22nakamorit <[email protected]>
2022-10-14 04:07 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
2022-10-14 04:26 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
2022-10-14 08:35 ` Re: Fix error message for MERGE foreign tables Michael Paquier <[email protected]>
2022-10-14 08:47 ` Re: Fix error message for MERGE foreign tables Alvaro Herrera <[email protected]>
2022-10-14 09:24 ` Re: Fix error message for MERGE foreign tables Alvaro Herrera <[email protected]>
2022-10-14 11:19 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
2022-10-14 13:07 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
2022-10-14 14:43 ` Re: Fix error message for MERGE foreign tables Tom Lane <[email protected]>
2022-10-17 02:07 ` Re: Fix error message for MERGE foreign tables Richard Guo <[email protected]>
2023-09-25 05:01 [PATCH v8 7/7] Allow to print raw parse tree. Tatsuo Ishii <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox