rom tbl2 limit 1) from tbl;
>
> > BTW, though you mentioned the risk of deadlocks, even when there
> > are no subquery, deadlock can occur in the current patch.
> >
> > For example, lock a table T in Session1, and then lock a view V
> > whose base relation is T in
ed the risk of deadlocks, even when there
are no subquery, deadlock can occur in the current patch.
For example, lock a table T in Session1, and then lock a view V
whose base relation is T in Session2. Session2 will wait for
Session1 to release the lock on T. After this, when Session1 try to
lock
SERT ON v1 FOR EACH ROW EXECUTE
PROCEDURE fnc();
CREATE TRIGGER
test=# BEGIN;
BEGIN
test=# LOCK TABLE v1;
ERROR: cannot lock view "v1"
DETAIL: views that have an INSTEAD OF trigger are not lockable
test=# END;
ROLLBACK
Regards,
--
Yugo Nagata <nag...@sraoss.co.jp>
diff --git a/do
SpinLockRelease(>mutex);
> 444 +
> 445 + return message_len;
This can return slot->len directly and the variable message_len is
unnecessary. However, if we handle the "too long message" error
in this function as suggested above, this does not have to
return anything.
Reg
--
> Append (cost=0.00..96.50 rows=50 width=4) (actual time=0.017..0.078 rows=2
> loops=1)
>-> Seq Scan on h1 (cost=0.00..48.25 rows=25 width=4) (actual
> time=0.015..0.019 rows=1 loops=1)
> Fil
On Tue, 15 Aug 2017 16:23:35 -0400
Peter Eisentraut <peter.eisentr...@2ndquadrant.com> wrote:
> On 7/27/17 20:52, Yugo Nagata wrote:
> > 175 /* Check if we support requested protocol */
> > 176 if (data->protocol_version != LOGICALREP_PROTO_VERSION_NUM)
>
On Tue, 15 Aug 2017 15:17:06 -0400
Peter Eisentraut <peter.eisentr...@2ndquadrant.com> wrote:
> On 8/1/17 02:28, Yugo Nagata wrote:
> > When reading the logical replication code, I found that the following
> > part could be improved a bit. In the f
On Mon, 7 Aug 2017 09:46:56 -0400
Peter Eisentraut <peter.eisentr...@2ndquadrant.com> wrote:
> On 7/27/17 20:51, Yugo Nagata wrote:
> > When we run ALTER SUBSCRIPTION ... REFRESH PUBLICATION and there is
> > an unkown table at local, it says;
> >
> > NOTI
shii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese:http://www.sraoss.co.jp
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql
m not sure
whether these call are expensive enough to fix. Is it worth to fix?
A patch attached.
Regards,
--
Yugo Nagata <nag...@sraoss.co.jp>
diff --git a/src/backend/replication/logical/launcher.c b/src/backend/replication/logical/launcher.c
index d165d51..4816a5b 100644
--- a/src/backend/repli
protocol %d or lower". Is this intentional?
Or should this be fixed as below?
176 if (data->protocol_version > LOGICALREP_PROTO_VERSION_NUM)
Attached is a simple patch in case of fixing.
Regards,
--
Yugo Nagata <nag...@sraoss.co.jp>
diff --git a/src/backend/replication/pgoutput/pgoutpu
.
Regards,
--
Yugo Nagata <nag...@sraoss.co.jp>
diff --git a/src/backend/commands/subscriptioncmds.c b/src/backend/commands/subscriptioncmds.c
index 6dc3f6e..5a7e6d5 100644
--- a/src/backend/commands/subscriptioncmds.c
+++ b/src/backend/commands/subscriptioncmds.c
@@ -573,9 +
On Thu, 27 Jul 2017 14:38:29 +0900
Masahiko Sawada <sawada.m...@gmail.com> wrote:
> On Thu, Jul 27, 2017 at 10:14 AM, Yugo Nagata <nag...@sraoss.co.jp> wrote:
> > Hi,
> >
> > I found that postgresql.conf.sample is missing a comment
> > to note that c
Hi,
I found that postgresql.conf.sample is missing a comment
to note that changing max_logical_replication_workers requires
restart of the server.
Other such parameters has the comments, so I think the new
parameter also needs this. Attached is a simple patch to fix
this.
Regards,
--
Yugo
On Fri, 21 Jul 2017 10:31:57 -0300
FabrÃzio de Royes Mello <fabriziome...@gmail.com> wrote:
> On Fri, Jul 21, 2017 at 9:35 AM, Yugo Nagata <nag...@sraoss.co.jp> wrote:
> >
> > On Fri, 21 Jul 2017 09:53:19 +0800
> > Craig Ringer <cr...@2ndquadrant.com> wr
On Fri, 21 Jul 2017 04:58:47 -0700
Andres Freund <and...@anarazel.de> wrote:
> Hi,
>
> (please don't top-reply on this list)
>
> On 2017-07-19 14:04:39 +0900, Yugo Nagata wrote:
> > On Tue, 18 Jul 2017 10:10:49 -0400
> > Tom Lane <t...@sss.pgh.pa.us> wrot
have run yet.
Thank you for your suggestion. Certainly, we can do the similar job of a
session-start hook using these existing hooks, although these hooks are
triggered when the first query is executed not when the session is started.
Now I come to think that an additional hook is not need.
Thanks
On Fri, 21 Jul 2017 10:11:05 +0800
Craig Ringer <cr...@2ndquadrant.com> wrote:
> On 20 July 2017 at 21:33, Yugo Nagata <nag...@sraoss.co.jp> wrote:
>
> > On Thu, 20 Jul 2017 11:02:25 +0200
> > Michael Paquier <michael.paqu...@gmail.com> wrote:
> >
>
macros were modified by the following commit,
but the comment were not.
commit dfda6ebaec6763090fb78b458a979b558c50b39b
Author: Heikki Linnakangas <heikki.linnakan...@iki.fi>
Date: Sun Jun 24 18:06:38 2012 +0300
Regards,
--
Yugo Nagata <nag...@sraoss.co.jp>
diff --git a/src/include/acce
he logical
xlog file, and the last 8 characters indicate the sequencial number of
the segment in this xlog.
Regards,
> --
> Michael
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.post
example of this hook that changes work_mem values for sessions
of a specific database.
I would appreciate hearing your opinion on this hook.
Regards,
--
Yugo Nagata <nag...@sraoss.co.jp>
diff --git a/src/backend/tcop/postgres.c b/src/backend/tcop/postgres.c
index b8d860e..7a1fa3b
se that have
> > outstanding ones.
>
> If somebody wanted to do the work, that'd be a viable answer IMO. You'd
> really want to not wake backends that have nothing more to send, but
> I agree that it'd be possible to advertise that in shared memory.
>
> r
pgsent_report_sent() again with a delay
after the last DML to make sure to send the statistics. The attached patch
implements this.
Any comments would be appreciated.
Regards,
--
Yugo Nagata <nag...@sraoss.co.jp>
diff --git a/src/backend/tcop/postgres.c b/src/backend/tcop/postgres.c
index b8d860e..9
On Fri, 30 Jun 2017 20:17:39 +0900
Masahiko Sawada <sawada.m...@gmail.com> wrote:
> On Fri, Jun 30, 2017 at 7:01 PM, Yugo Nagata <nag...@sraoss.co.jp> wrote:
> > Hi,
> >
> > The documentation says that a subscription that has a replication slot
> > ca
Hi,
The documentation says that a subscription that has a replication slot
cannot be dropped in a transaction block, but it is not allowed even
outside of a transaction block. Attached is a patch to fix it.
Regards,
--
Yugo Nagata <nag...@sraoss.co.jp>
diff --git a/doc/src/sg
ge-id/20170624000156.74ca9485.nagata%40sraoss.co.jp
>
> Regards
> Remi
>
>
> 2017-06-28 12:17 GMT+02:00 Yugo Nagata <nag...@sraoss.co.jp>:
>
> > Hi,
> >
> > Attached is a patch of pg_reload_backend that is a function signaling
> > SIGHUP to
On Wed, 28 Jun 2017 13:35:12 +0200
Dmitry Dolgov <9erthali...@gmail.com> wrote:
> > On 28 June 2017 at 12:17, Yugo Nagata <nag...@sraoss.co.jp> wrote:
> >
> > Hi,
> >
> > Attached is a patch of pg_reload_backend that is a function signaling
> >
/message-id/CAB7nPqT4y8-QoGKEugk99_tFuEOtAshcs5kxOeZ_0w27UtdGyA%40mail.gmail.com
--
Yugo Nagata <nag...@sraoss.co.jp>
diff --git a/src/backend/catalog/system_views.sql b/src/backend/catalog/system_views.sql
index 0fdad0c..3a9a020 100644
--- a/src/backend/catalog/system_views.sql
+++ b/src/b
On Fri, 23 Jun 2017 19:43:35 -0400
Stephen Frost <sfr...@snowman.net> wrote:
> Alvaro, all,
>
> * Alvaro Herrera (alvhe...@2ndquadrant.com) wrote:
> > Yugo Nagata wrote:
> >
> > > I tried to make it. Patch attached.
> > >
> > > It is ea
On Sat, 24 Jun 2017 08:09:52 +0900
Michael Paquier <michael.paqu...@gmail.com> wrote:
> On Sat, Jun 24, 2017 at 5:07 AM, Alvaro Herrera
> <alvhe...@2ndquadrant.com> wrote:
> > Yugo Nagata wrote:
> >
> >> I tried to make it. Patch attached.
> >>
>
On Fri, 23 Jun 2017 09:54:17 -0400
Tom Lane <t...@sss.pgh.pa.us> wrote:
> Yugo Nagata <nag...@sraoss.co.jp> writes:
> > When we create a range partitioned table, we cannot use
> > a column more than once in the partition key.
>
> > postgres=# create ta
On Thu, 22 Jun 2017 14:08:30 +0900
Michael Paquier <michael.paqu...@gmail.com> wrote:
> On Thu, Jun 22, 2017 at 1:52 PM, Yugo Nagata <nag...@sraoss.co.jp> wrote:
> > On Thu, 22 Jun 2017 12:05:19 +0900
> > Michael Paquier <michael.paqu...@gmail.com> wrote:
>
On Fri, 23 Jun 2017 15:57:54 +0900
Yugo Nagata <nag...@sraoss.co.jp> wrote:
> Hi,
>
> When we create a range partitioned table, we cannot use
> a column more than once in the partition key.
>
> postgres=# create table t (i int) partition by range(i,i);
> ERROR: c
e internal of partitioning?
If not, we might not need to check column that apears more than once
in the partition key.
Regards,
--
Yugo Nagata <nag...@sraoss.co.jp>
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://ww
On Fri, 23 Jun 2017 13:41:15 +0900
Yugo Nagata <nag...@sraoss.co.jp> wrote:
> On Tue, 6 Jun 2017 13:03:58 +0530
> amul sul <sula...@gmail.com> wrote:
>
>
> > Updated patch attached.
>
> I looked into the latest patch (v13) and have some comments
> a
On Thu, 22 Jun 2017 13:55:26 -0400
Alvaro Herrera <alvhe...@2ndquadrant.com> wrote:
> Yugo Nagata wrote:
> > Hi,
> >
> > As I report in another thread[1], I found the autovacuum launcher occurs
> > the following error in PG 10 when this
ing the comment of pg_get_partkeydef() is missing.
* pg_get_partkeydef
*
* Returns the partition key specification, ie, the following:
*
* PARTITION BY { RANGE | LIST } (column opt_collation opt_opclass [, ...])
*/
Datum
pg_get_partkeydef(PG_FUNCTION_ARGS)
{
Regards,
>
> Regards,
> Amul Sul
--
Yugo Nagata <nag...@sraoss.co.jp>
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Thu, 22 Jun 2017 14:14:53 +0530
Ashutosh Bapat <ashutosh.ba...@enterprisedb.com> wrote:
> On Wed, Jun 21, 2017 at 7:48 PM, Simon Riggs <si...@2ndquadrant.com> wrote:
> > On 21 June 2017 at 16:15, Yugo Nagata <nag...@sraoss.co.jp> wrote:
> >> On Wed, 21 Jun 2
age truncation seems to be a kind of helpful
information rather than a likely problem as long as pg_terminated_backend
exits successfully.
https://www.postgresql.org/docs/10/static/runtime-config-logging.html#runtime-config-severity-levels
> --
> Michael
--
Yugo Nagata <nag..
On Wed, 21 Jun 2017 15:17:20 -0400
Peter Eisentraut <peter.eisentr...@2ndquadrant.com> wrote:
> On 6/21/17 13:03, Yugo Nagata wrote:
> > As I report in another thread[1], when the logical replication launcher
> > is terminated by SIGTERM, it never been restarted a
On Thu, 22 Jun 2017 13:12:48 +0900
Michael Paquier <michael.paqu...@gmail.com> wrote:
> On Wed, Jun 21, 2017 at 9:15 PM, Yugo Nagata <nag...@sraoss.co.jp> wrote:
> > This errors continue until this process is terminated or the server is
> > restarted.
> >
>
On Thu, 22 Jun 2017 12:05:19 +0900
Michael Paquier <michael.paqu...@gmail.com> wrote:
> On Thu, Jun 22, 2017 at 11:52 AM, Andres Freund <and...@anarazel.de> wrote:
> > On 2017-06-22 11:49:47 +0900, Yugo Nagata wrote:
> >> I agree that we can kill theses proces
On Wed, 21 Jun 2017 11:04:34 -0400
Robert Haas <robertmh...@gmail.com> wrote:
> On Wed, Jun 21, 2017 at 7:56 AM, Yugo Nagata <nag...@sraoss.co.jp> wrote:
> > I have found that we can cancel/terminate autovacuum launchers and
> > background worker processes by pg_cancel
: logical replication launcher (PID 11526) exited with
exit code 1
If we don't want to get this message, we need more fixes in
CleanupBackgroundWorker()
or around it.
[1]
https://www.postgresql.org/message-id/20170621205657.61d90605.nagata%40sraoss.co.jp
--
Yugo Nagata <nag...@sraoss.co.jp>
On Wed, 21 Jun 2017 16:18:50 +0200
Simon Riggs <si...@2ndquadrant.com> wrote:
> On 21 June 2017 at 16:15, Yugo Nagata <nag...@sraoss.co.jp> wrote:
> > On Wed, 21 Jun 2017 19:08:35 +0530
> > Kuntal Ghosh <kuntalghosh.2...@gmail.com> wrote:
> >
> >> O
users that the message they can read was
truncated one. Or, maybe we should prohibit too long message
is passed in pg_teminate_backend()
> --
> Michael
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> h
On Wed, 21 Jun 2017 19:08:35 +0530
Kuntal Ghosh <kuntalghosh.2...@gmail.com> wrote:
> On Wed, Jun 21, 2017 at 6:05 PM, Yugo Nagata <nag...@sraoss.co.jp> wrote:
> >
> > Attached is a patch for the documentation fix.
> >
> Please attach the patch as well. :-
er is kept per backend for the
> message. If deemed too costly, keeping a central buffer from which slabs are
> allocated can be done (but seemed rather complicated for little gain compared
> to the quite moderate memory spend.)
>
> cheers ./daniel
>
--
Yugo
y.html#hot-standby-admin
--
Yugo Nagata <nag...@sraoss.co.jp>
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
,
[1]
https://www.postgresql.org/message-id/20170621205657.61d90605.nagata%40sraoss.co.jp
--
Yugo Nagata <nag...@sraoss.co.jp>
diff --git a/src/backend/postmaster/autovacuum.c b/src/backend/postmaster/autovacuum.c
index 89dd3b3..8a41a98 100644
--- a/src/backend/postmaster/autovacuum.c
+++
SIGTERM, this exits with
exitstatus 0,
so this is not restarted by the postmaster.
[2]
On the other hand, when we use pg_cancel_backend for autovacuum launcher,
it causes the following error. I'll report the detail in another thread.
ERROR: can't attach the same segment more than once
-
Attached is a patch to fix it.
Regards,
--
Yugo Nagata <nag...@sraoss.co.jp>
release_note_pg_current_logfile.pach
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Hi,
I found a typo in the PG10 release note and attached is a patch
to fix it.
Regards,
--
Yugo Nagata <nag...@sraoss.co.jp>
diff --git a/doc/src/sgml/release-10.sgml b/doc/src/sgml/release-10.sgml
index b10086bd..f3e4a70 100644
--- a/doc/src/sgml/release-10.sgml
+++ b/doc/src/sgml/rele
Hi,
Attached is a simple patch to fix a documentation typo in
the ALTER TABLE example.
Regards,
--
Yugo Nagata <nag...@sraoss.co.jp>
diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml
index 56ea830..4c61c44 100644
--- a/doc/src/sgml/ref/alter_table.sgml
Hi,
Attached is a patch fixing simple typos in the CREATE TRIGGER document.
--
Yugo Nagata <nag...@sraoss.co.jp>
diff --git a/doc/src/sgml/ref/create_trigger.sgml b/doc/src/sgml/ref/create_trigger.sgml
index 24195b3..c5f7c75 100644
--- a/doc/src/sgml/ref/create_trigger.sgml
+++ b/doc/sr
On Fri, 14 Apr 2017 09:05:14 -0400
Robert Haas <robertmh...@gmail.com> wrote:
> On Fri, Apr 14, 2017 at 4:23 AM, Yugo Nagata <nag...@sraoss.co.jp> wrote:
> > On Thu, 13 Apr 2017 16:40:29 -0400
> > Robert Haas <robertmh...@gmail.com> wrote:
> >> On Fri,
On Thu, 13 Apr 2017 16:40:29 -0400
Robert Haas <robertmh...@gmail.com> wrote:
> On Fri, Mar 17, 2017 at 7:57 AM, Yugo Nagata <nag...@sraoss.co.jp> wrote:
> > I also understanded that my design has a problem during pg_dump and
> > pg_upgrade, and that some informatio
d some comments are added.
Thanks,
--
Yugo Nagata <nag...@sraoss.co.jp>
hash_partition.patch.v2
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
e of the things you can add to an ereport() call.
>
> What is the function name?
>
> Regards,
>
> --
> Masahiko Sawada
> NIPPON TELEGRAPH AND TELEPHONE CORPORATION
> NTT Open Source Software Center
--
Yugo Nagata <nag...@sraoss.co.jp>
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ndquadrant.com>
Date: Fri Mar 3 19:18:25 2017 +0530
Allow vacuums to report oldestxmin
Regards,
Yugo Nagata
On Tue, 28 Feb 2017 16:40:28 +0900
Masahiko Sawada <sawada.m...@gmail.com> wrote:
> On Fri, Feb 24, 2017 at 1:30 AM, Masahiko Sawada <sawada.m...@gmail.com>
On Thu, 2 Mar 2017 18:33:42 +0530
amul sul <sula...@gmail.com> wrote:
Thank you for the patch. This is very interesting. I'm going to look
into your code and write a feedback later.
> On Wed, Mar 1, 2017 at 3:50 PM, Yugo Nagata <nag...@sraoss.co.jp> wrote:
>
> >
es to be accepted in current commitfest. Naturally if community
> will come to a consensus regarding keywords, whether all partitions
> should be created automatically, etc :)
>
> [1] http://afiskon.ru/s/dd/20cbe21934_regression.diffs.txt
> [2] http://afiskon.ru/s/76/a4fb71739c_full-b
On Wed, 1 Mar 2017 10:52:58 +0530
amul sul <sula...@gmail.com> wrote:
> On Tue, Feb 28, 2017 at 8:03 PM, Yugo Nagata <nag...@sraoss.co.jp> wrote:
> > Hi all,
> >
> > Now we have a declarative partitioning, but hash partitioning is not
> > implemented yet.
On Wed, 1 Mar 2017 10:30:09 +0530
Rushabh Lathia <rushabh.lat...@gmail.com> wrote:
> On Tue, Feb 28, 2017 at 8:03 PM, Yugo Nagata <nag...@sraoss.co.jp> wrote:
>
> > Hi all,
> >
> > Now we have a declarative partitioning, but hash partitioning is not
> >
Hi Ammit,
On Wed, 1 Mar 2017 11:14:15 +0900
Amit Langote <langote_amit...@lab.ntt.co.jp> wrote:
> Nagata-san,
>
> On 2017/02/28 23:33, Yugo Nagata wrote:
> > Hi all,
> >
> > Now we have a declarative partitioning, but hash partitioning is not
> > implemen
ou for registering it to the commitfest. I have added me as an auther.
>
> [1] https://commitfest.postgresql.org/13/1059/
>
> On Tue, Feb 28, 2017 at 11:33:13PM +0900, Yugo Nagata wrote:
> > Hi all,
> >
> > Now we have a declarative partitioning, but hash partitionin
=0.00..61.00 rows=13 width=4)
Filter: ((abs(hashint4(i)) % 3) = 2)
(5 rows)
Best regards,
Yugo Nagata
--
Yugo Nagata <nag...@sraoss.co.jp>
diff --git a/src/backend/catalog/heap.c b/src/backend/catalog/heap.c
index 41c0056..3820920 100644
--- a/src/backend/catalog/heap.c
+++ b/src
ent relation
This seems better. Patch is updated.
Thanks,
--
Yugo Nagata <nag...@sraoss.co.jp>
diff --git a/src/include/nodes/execnodes.h b/src/include/nodes/execnodes.h
index 6332ea0..af3367a 100644
--- a/src/include/nodes/execnodes.h
+++ b/src/include/nodes/execnodes.h
@@ -326,6 +326,
Hi,
I found that a comment for PartitionRoot in ResultRelInfo is missing.
Although this is trivial, since all other members have comments, I
think it is needed. Attached is the patch to fix it.
Regards,
Yugo Nagata
On Tue, 27 Dec 2016 17:59:05 +0900
Amit Langote <langote_amit...@lab.ntt.co
greSQL Company
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
--
Yugo Nagata <nag...@sraoss.co.jp>
diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/d
On Wed, 8 Feb 2017 14:54:17 -0500
Robert Haas <robertmh...@gmail.com> wrote:
> On Tue, Feb 7, 2017 at 4:22 AM, Yugo Nagata <nag...@sraoss.co.jp> wrote:
> > I found typos "pg_statistics" in REL9_6_STABLE, but that has been
> > fixed in the master br
# BEGIN;
> BEGIN
> postgres=# INSERT INTO ft1_lt VALUES *(3)*; -- Violates constraint
> INSERT 0 1
> postgres=# INSERT INTO ft2_lt VALUES *(3)*; -- Violates constraint
> INSERT 0 1
> postgres=# COMMIT;
> .
> .
> .
>
> postgres=# select datid,datname,pid,wait_eve
c0fecb6d08
I think it would be better to backport this to other branches.
Regards,
--
Yugo Nagata <nag...@sraoss.co.jp>
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
18:24:20 2014 +0100
Lockless StrategyGetBuffer clock sweep hot path.
Attached a patch.
--
Yugo Nagata <nag...@sraoss.co.jp>
diff --git a/src/backend/storage/buffer/freelist.c b/src/backend/storage/buffer/freelist.c
index b68ab20..5d0a636 100644
--- a/src/backend/storage/buffer/free
for the current
implementation?
Best regards,
--
Yugo Nagata <nag...@sraoss.co.jp>
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Hi,
I found that codes about T_PrivGrantee was removed
by the following commit;
http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=31eae6028eca4365e7165f5f33fee1ed0486aee0
but T_PrivGrantee is left in NodeTag in src/include/nodes/nodes.h.
Is it intended?
--
Yugo Nagata <
. Is this better than the previous one?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Yugo Nagata nag...@sraoss.co.jp
to_regclass.patch.v7
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
On Thu, 23 Jan 2014 13:19:37 +0200
Marti Raudsepp ma...@juffo.org wrote:
Resending to Tatsuo Ishii and Yugo Nagata, your email server was
having problems yesterday:
Thanks for resending!
This is the mail system at host sraigw2.sra.co.jp.
yug...@sranhm.sra.co.jp: mail
On Wed, 22 Jan 2014 20:04:12 +0900 (JST)
Tatsuo Ishii is...@postgresql.org wrote:
On Tue, Jan 14, 2014 at 9:28 AM, Yugo Nagata nag...@sraoss.co.jp wrote:
Here is the patch to implement to_regclass, to_regproc, to_regoper,
and to_regtype.
+ static Datum regclass_guts(char
and post-9.3
using a condition of conn-sversion = 90300.
Agreed. I'll fix it like that.
4) src/test/examples/testlo64.c added for 64-bit API example(Yugo Nagata)
Comments and suggestions are welcome.
miscellaneous comments are below.
Regression test is helpful. Even though no need
80 matches
Mail list logo