On 10/30/2017 01:36 PM, tushar wrote:
On 10/30/2017 09:02 AM, Amit Kapila wrote:
Thanks a lot Tushar for testing this patch. In the latest patch, I
have just rebased some comments, there is no code change, so I don't
expect any change in behavior, but feel free to test it once again.
T
On 10/30/2017 09:02 AM, Amit Kapila wrote:
Thanks a lot Tushar for testing this patch. In the latest patch, I
have just rebased some comments, there is no code change, so I don't
expect any change in behavior, but feel free to test it once again.
Thanks Amit. Sure.
--
regards,t
T * FROM ( SELECT n from tv where n= (select * from
(select n from tv limit 1) c)) as c ;
n
--
3713
(1 row)
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgres
from (select n from tv limit 1) c)) as c ;
n
--
3713
(1 row)
This time , query is started showing wrong result. Is this an expected
behavior and if yes -then how to get the correct result ?
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Comp
On 10/09/2017 03:26 PM, Amit Kapila wrote:
I have reverted the check
in the attached patch.
I have applied this patch against PG HEAD and run sqlsmith and analyzed
results . didn't find any specific failures against this patch.
--
regards,tushar
EnterpriseDB https://www.enterprised
l functions can only be executed during recovery.
CONTEXT: parallel worker
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgr
=> tps= 8011.784839(3.30+% vs. head)
Case 4-TIME=1500
PG HEAD =>tps = 40365.099628 (excluding connections establishing)
PG HEAD+patch =>tps= 42385.372848(5.00+% vs. head)
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
On 09/27/2017 05:29 PM, tushar wrote:
After discussion with Jeevan Ladhe, we created a sql query which
contain lots of inbuild function and tested that against pgbench
with master v/s patch and found an improvement
I tested it again and found around +2% improvement
./pgbench -c 8 -j 8 -f
establishing).
PG HEAD+patch - tps = 5751.745767(8.32+% vs. head)
pgbench -c 8 -j 8 -f /tmp/mytest.sql -T 500 postgres
PG Head - tps = 7701.176220(excluding connections
establishing).
PG HEAD+patch - tps = 7953.934043(3.27+% vs. head)
--
regards,tushar
EnterpriseDB https
head)
pgbench -M prepared -f /tmp/pgbench-many-cols.sql -T 700 postgres
PG Head - tps = 5640.314495(excluding connections establishing).
PG HEAD+patch - tps = 6012.223147 (6.59+% vs. head)
-- regards,tushar
EnterpriseDBhttps://www.enterprisedb.com/
The Enterprise PostgreSQL Company
--
d
SELECT
pg_catalog.binary_upgrade_set_next_pg_type_oid('16390'::pg_catalog.oid);
manually i am able to create all these objects .
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-
r0 TO regress_dep_user1;
REASSIGN OWNED BY regress_dep_user1 TO regress_dep_user0;
CREATE TABLE deptest1 (f1 int unique);
GRANT ALL ON deptest1 TO regress_dep_user1 WITH GRANT OPTION;
SET SESSION AUTHORIZATION regress_dep_user1;
GRANT ALL ON deptest1 TO regress_dep_user2;
v10 - run pg_upgrade.
--
cluster dump using pg_dumpall
"
--
-- Name: alt_lang1; Type: PROCEDURAL LANGUAGE; Schema: -; Owner: edb
--
CREATE OR REPLACE PROCEDURAL LANGUAGE alt_lang1;
ALTER PROCEDURAL LANGUAGE alt_lang1 OWNER TO edb;
"
Handler part is missing and due to that it is throwing an error ,if we
try to exe
ss_oid('16392'::pg_catalog.oid);
CREATE VIEW "v3_9166" AS
SELECT "seq_9166"."sequence_name",
"seq_9166"."last_value",
"seq_9166"."start_value",
"seq_9166"."increment_by",
"s
g_catalog.oid);
CREATE VIEW "ttt1" AS
SELECT "e"."n"
FROM ("t" "e"
LEFT JOIN "t1" "d");
"
I think -this issue should be there in the older branches as well but
not checked that.
--
regards,tushar
Ente
default (changed at the time of ./configure) +
different wal_segment_size (at the time of initdb) .
Things looks fine.
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
: *** [pg_filedump.o] Error 1
[centos@centos-cpula pg_filedump]$
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
_ctl() failed: Bad file
descriptor
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
version: 0
Values to be changed:
First log segment after reset:00010002
If these values seem acceptable, use -f to force reset.
[centos@centos-cpula ~]$
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
--
Sent via pgsql-
: could not open directory "pg_wal": No such file or directory
[centos@centos-cpula bin]$
Steps to reproduce-
installed PG v9.6
installed PG v10
go to bin directory of v10 and run pg_resetwal , provide -D = data
directory of v9.6.
--
regards,tushar
EnterpriseDB https://www.enterprised
t count(*) from pgbench_history ;
count
-
1090959
(1 row)
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgres
ATAL: database "postgre"
does not exist
postgres=#
but such checking is not done at the time of alter subscription ..
connection
postgres=# alter subscription c1 connection 'port=4000';
ALTER SUBSCRIPTION
postgres=# alter subscription c1 connection 'dbname=cc
On 05/25/2017 03:38 PM, tushar wrote:
While performing - Alter subscription..SET , I found that NOTICE
message is coming duplicate next time , which is not needed anymore.
There is an another example - where i am getting "ERROR: subscription
table 16435 in subscription 16684 does not
On 05/25/2017 04:40 PM, Masahiko Sawada wrote:
I think you did ALTER SUBSCRIPTION while table sync for 100 tables is
running, right?
Yes, i didn't wait too much while executing the commands.
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Co
ON
now again fire the same sql query
postgres=# alter subscription sub set publication pub1 refresh;
NOTICE: removed subscription for table public.t78
ALTER SUBSCRIPTION
This notice message should not come as t.78 is already removed from
earlier same command.
--
regards,tushar
E
op subscription sub;
NOTICE: dropped replication slot "sub" on publisher
DROP SUBSCRIPTION
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
d standby).
reproducing this issue is not consistent. Out of 5 times, i am able to
reproduce it 2 times only.
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
files.tar.bz2
Description: application/bzip
--
Sent via pgsql-hackers mailing li
On 05/23/2017 06:25 PM, Robert Haas wrote:
Just out of curiosity, what happens if you try it with the attached patch?
Thanks, issue seems to be fixed after applying your patch.
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
--
Sent via pgsql
skip refresh ;
ALTER SUBSCRIPTION
s=#
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ast(null as tid),
cast(null as tid)) as integer)) is NULL)
limit 143) as subq_0
where pg_catalog.pg_rotate_logfile() is NULL) as subq_1
where 50 <> 45;
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterpri
.
postgres=#
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
regress]$ pg_dump -Fp ntest > /tmp/a.a
cat /tmp/a.a
SET search_path = public, pg_catalog;
--
-- Name: e1; Type: VIEW; Schema: public; Owner: centos
--
CREATE VIEW e1 AS
SELECT abc.n
FROM information_schema.abc;
--
regards,tushar
tos;
[centos@centos-cpula regress]$
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
x27; has been set against partition table ,which is not
supported.
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ate the subscription from the slot.
expected = "HINT: Use ALTER SUBSCRIPTION ... *SET* (slot_name = NONE)
to disassociate the subscription from the slot."
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
cation apply for
subscription m1 started
2017-05-16 14:04:53.403 BST [18224] ERROR: could not start WAL
streaming: ERROR: replication slot name "" is too short
Is this error message (ERROR: replication slot name "" is too short )
is expected now ?
--
regards,tushar
Enterp
T ENABLED SLOT_NAME
synchronous_commit option is not visible
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mail
table states
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.
!>
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterpr
try to execute the same syntax against psql terminal
postgres=# CREATE PUBLICATION abc FOR ALL TABLES WITH (publish =
'insert, , ');
ERROR: invalid publish list
Same is valid for pg_dumpall as well..
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise Postgre
got removed)
postgres=# alter subscription sub set publication pub refresh;
NOTICE: removed subscription for table public.t1
NOTICE: removed subscription for table public.t2
ALTER SUBSCRIPTION
I think - in publication too ,we should provide NOTICE messages.
--
regards,tushar
EnterpriseDB
e to drop it later.
postgres=# drop subscription sub;
ERROR: could not drop the replication slot "nowhere" on publisher
DETAIL: The error was: ERROR: replication slot "nowhere" does not exist
postgres=#
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Ent
on for table public.t
ALTER SUBSCRIPTION
Is this an expected behavior ? if we cannot publish then how can we
add subscription for it.
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers
er (Y)
X - insert more records into table 't'
Y - check the row count , rows have been migrated from X .
Is it the right behavior in this case where nocopy data option is set ?
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
--
Sent via
al
decoding
2017-05-09 10:51:44.038 BST [1801] LOG: worker process: logical
replication worker for subscription 16393 (PID 2738) exited with exit code 1
I think -we should throw an error while creating subscription.
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
T
ostgres=# select * from test;
n
---
1
1
(2 rows)
Y server
postgres=# select * from test;
n
---
1
(1 row)
I think probably syntax of alter subscription is not correct but
surprisingly it is not throwing an error.
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise
On 05/04/2017 03:53 PM, tushar wrote:
We can see statement_timeout is working but it is taking some extra
time,not sure this is an expected behavior in above case or not.
This is only when remote server is involved . in case when both the
servers are on the same machine , then this is working
cancel() -- connect() failed:
Connection timed out
ERROR: canceling statement due to statement timeout
Time: 83014.503 ms (01:23.015)
We can see statement_timeout is working but it is taking some extra
time,not sure this is an expected behavior in above case or not.
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
which seems
probably insane.
No, i have not changed any parameters except logging_collector=on in
postgresql.conf file.
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make ch
the request.
The connection to the server was lost. Attempting reset: Failed.
!> \q
here is the stack trace -
[centos@tushar-centos bin]$ gdb -q -c mdata/core.4254
/home/centos/pg10_28march/postgresql/edbpsql/bin/postgres
Reading symbols from
/home/centos/pg10_28march/postgresql/edbpsql/bin/pos
On 03/14/2017 11:14 AM, Beena Emerson wrote:
Hello,
Attached is the updated patch. It fixes the issues and also updates
few code comments.
Can you please check with the new patch?
Thanks, both issues has been fixed now.
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The
formed initdb with switch "--wal-segsize 4"
start the server
run pg_basebackup
[centos@tushar-centos bin]$ ./pg_basebackup -v -D /tmp/myslave
*** glibc detected *** ./pg_basebackup: free(): invalid pointer:
0x08da7f00 ***
=== Backtrace: =
/lib/libc.so.6[0xae7e31]
/home/c
On 02/01/2017 06:50 PM, Amit Kapila wrote:
Used large table parallel index scans (both forward and backward
scans). These tests have been done by Tushar and you can find
detailed report up thread [2]. Apart from that, the patch has been
tested with TPC-H queries at various scale factors and it
On 02/01/2017 06:50 PM, Amit Kapila wrote:
Used large table parallel index scans (both forward and backward
scans). These tests have been done by Tushar and you can find
detailed report up thread [2]. Apart from that, the patch has been
tested with TPC-H queries at various scale factors and it
we have generated the LCOV (code coverage) report and
compared the files which are changed for this.
You can see the numbers for "with_patch" V/s "with_patch+TestCases"
(.pdf file is attached)
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterpris
On 01/10/2017 05:16 PM, Dilip Kumar wrote:
Please try attached patch and confirm from your
side.
Thanks,issue seems to be fixed now.
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers
On 01/10/2017 11:29 AM, tushar wrote:
On 01/09/2017 07:22 PM, Dilip Kumar wrote:
Thanks, Tushar. I have fixed it. The defect was in 0002. I have also
observed another issue related to code refactoring, Actually, there
was some code present in 0001 which supposed to be in 0003.
Thanks, I have
On 01/09/2017 07:22 PM, Dilip Kumar wrote:
Thanks, Tushar. I have fixed it. The defect was in 0002. I have also
observed another issue related to code refactoring, Actually, there
was some code present in 0001 which supposed to be in 0003.
Thanks, I have checked at my end and it is fixed now
'--enable-cassert'
switch in the configure. We are able to reproduce it only with
--enable-cassert' .
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
ch_path=pg_catalog -c exit_on_error=true template1 > /dev/null
child process exited with exit code 139
initdb: removing data directory "data"
[centos@tusharcentos7 bin]$
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
--
Sent via pg
"centos") at postgres.c:4072
#27 0x0079718f in BackendRun (port=0x1e69730) at postmaster.c:4275
#28 0x00796917 in BackendStartup (port=0x1e69730) at
postmaster.c:3947
#29 0x0079302e in ServerLoop () at postmaster.c:1704
#30 0x0079266d in PostmasterMai
On 12/23/2016 05:38 PM, Robert Haas wrote:
So why are you reporting it here rather than on a separate thread?
We found it -while testing parallel index scan and later it turned out
to be crash in general.
Sure- make sense ,will do that.
--
regards,tushar
--
Sent via pgsql-hackers mailing
On 12/22/2016 01:35 PM, tushar wrote:
On 12/22/2016 09:49 AM, Amit Kapila wrote:
I think you can focus on the handling of array scan keys for testing.
In general, one of my colleagues has shown interest in testing this
patch and I think he has tested as well but never posted his findings.
I
On 04/21/2016 08:36 AM, Robert Haas wrote:
Nice catch, Tushar. Thanks for the patch, Fabrízio. Committed.
Thanks, Verified against the latest sources of PG9.6 - issue has been
fixed now.
--
regards,tushar
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
ouble precision
);
"
--
regards,tushar
parallel_degree i.e
parallel_degree = 20, max_parallel_degree=10 => [ select query
accepting 10 workers ]
but in general where table doesn't have parallel_degree set and
max_parallel_degree is
set to 10 then select query is showing only 2 workers .
--
regards,tushar
--
Sent via pgsql-
better to throw the error at the time of setting
>>max_parallel_degree, if not supported ?
>
>+1
It surprises me that that request overflowed size_t. I guess we
should look into why that's happening. Did you test this on a 32-bit
system?
No, I tested on 64 bit machine.
--
r
;=1;
ERROR: requested shared memory size overflows size_t
if we remove the analyze keyword then query running successfully.
Expected = Is it not better to throw the error at the time of setting
max_parallel_degree, if not supported ?
--
regards,tushar
67 matches
Mail list logo