You can subscribe to this list here.
2010 |
Jan
|
Feb
|
Mar
|
Apr
(10) |
May
(17) |
Jun
(3) |
Jul
|
Aug
|
Sep
(8) |
Oct
(18) |
Nov
(51) |
Dec
(74) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2011 |
Jan
(47) |
Feb
(44) |
Mar
(44) |
Apr
(102) |
May
(35) |
Jun
(25) |
Jul
(56) |
Aug
(69) |
Sep
(32) |
Oct
(37) |
Nov
(31) |
Dec
(16) |
2012 |
Jan
(34) |
Feb
(127) |
Mar
(218) |
Apr
(252) |
May
(80) |
Jun
(137) |
Jul
(205) |
Aug
(159) |
Sep
(35) |
Oct
(50) |
Nov
(82) |
Dec
(52) |
2013 |
Jan
(107) |
Feb
(159) |
Mar
(118) |
Apr
(163) |
May
(151) |
Jun
(89) |
Jul
(106) |
Aug
(177) |
Sep
(49) |
Oct
(63) |
Nov
(46) |
Dec
(7) |
2014 |
Jan
(65) |
Feb
(128) |
Mar
(40) |
Apr
(11) |
May
(4) |
Jun
(8) |
Jul
(16) |
Aug
(11) |
Sep
(4) |
Oct
(1) |
Nov
(5) |
Dec
(16) |
2015 |
Jan
(5) |
Feb
|
Mar
(2) |
Apr
(5) |
May
(4) |
Jun
(12) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(4) |
2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
S | M | T | W | T | F | S |
---|---|---|---|---|---|---|
|
|
|
|
|
|
1
(5) |
2
|
3
(6) |
4
(5) |
5
(10) |
6
(5) |
7
(2) |
8
(2) |
9
|
10
|
11
(4) |
12
(13) |
13
(13) |
14
(29) |
15
|
16
|
17
(5) |
18
(2) |
19
(5) |
20
(7) |
21
(1) |
22
|
23
|
24
(1) |
25
(2) |
26
|
27
(6) |
28
(5) |
|
From: David E. W. <da...@ju...> - 2014-02-06 17:12:00
|
On Feb 5, 2014, at 5:33 PM, Tatsuo Ishii <is...@po...> wrote: > What about this? > > SELECT count(*) from > (SELECT has_function_privilege('%s', 'pgxc_version(text)', 'execute') > WHERE EXISTS(SELECT * FROM pg_catalog.pg_proc AS p WHERE p.proname = 'pgxc_version')) AS s" I don’t much care about permission, so I would just do SELECT TRUE FROM pg_catalog.pg_proc p JOIN pg_catalog.pg_namespace n ON p.pronamespace = n.oid WHERE nspname = 'pg_catalog' AND proname = 'pgxc_version'; Best, David |
From: Ahsan H. <ahs...@en...> - 2014-02-06 07:18:00
|
Abbas, Can you test this with 1.1? Perhaps we fixed this issue in the master which means that it will be part of 1.2 beta that is planned for this month. -- Ahsan On Wed, Feb 5, 2014 at 10:03 PM, David E. Wheeler <da...@ju...>wrote: > On Feb 4, 2014, at 10:18 PM, Abbas Butt <abb...@en...> > wrote: > > > I had to change the insert query a little bit and had to do some dummy > inserts in projects and changes too, but the query worked fine for me. BTW > I tried on current master, I am not sure which version you are using to > test. > > The 1.1 release. > > > Here are the queries I tried. > > > > After creating the three tables, I did > > > > insert into projects values('?', '?', DEFAULT, '?', '?'); > > > > insert into changes values('?', '?', '?', '?', DEFAULT, '?', '?', > clock_timestamp(), '?', '?'); > > > > INSERT INTO tags (tag_id, tag, project, change_id, note, committer_name, > committer_email, planned_at, planner_name, planner_email) > > SELECT tid, tg, proj, chid, n, name, email, at, pname, pemail FROM ( > VALUES ('?', '?', '?', '?', '?', '?', '?', clock_timestamp()::timestamptz, > '?', '?')) i(tid, tg, proj, chid, n, name, email, at, pname, pemail) LEFT > JOIN tags ON i.tid = tags.tag_id WHERE tags.tag_id IS NULL; > > On 1.1: > > dwheeler=# insert into sqitch.projects values('?', '?', DEFAULT, '?', '?'); > INSERT 0 1 > Time: 48.720 ms > dwheeler=# insert into sqitch.changes values('?', '?', '?', '?', DEFAULT, > '?', '?', clock_timestamp(), '?', '?'); > INSERT 0 1 > Time: 43.704 ms > dwheeler=# INSERT INTO sqitch.tags (tag_id, tag, project, change_id, note, > committer_name, committer_email, planned_at, planner_name, planner_email) > dwheeler=# INSERT INTO sqitch.tags (tag_id, tag, project, change_id, note, > committer_name, committer_email, planned_at, planner_name, planner_email) > dwheeler-# SELECT tid, tg, proj, chid, n, name, email, at, pname, pemail > FROM ( VALUES ('?', '?', '?', '?', '?', '?', '?', > clock_timestamp()::timestamptz, '?', '?')) i(tid, tg, proj, chid, n, name, > email, at, pname, pemail) LEFT JOIN sqitch.tags ON i.tid = tags.tag_id > WHERE tags.tag_id IS NULL; > ERROR: unexpected varno 6 in JOIN RTE 5 > Time: 4.064 ms > > Best, > > David > > > > ------------------------------------------------------------------------------ > Managing the Performance of Cloud-Based Applications > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. > Read the Whitepaper. > > http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > -- Ahsan Hadi Snr Director Product Development EnterpriseDB Corporation The Enterprise Postgres Company Phone: +92-51-8358874 Mobile: +92-333-5162114 Website: www.enterprisedb.com EnterpriseDB Blog: http://blogs.enterprisedb.com/ Follow us on Twitter: http://www.twitter.com/enterprisedb This e-mail message (and any attachment) is intended for the use of the individual or entity to whom it is addressed. This message contains information from EnterpriseDB Corporation that may be privileged, confidential, or exempt from disclosure under applicable law. If you are not the intended recipient or authorized to receive this for the intended recipient, any use, dissemination, distribution, retention, archiving, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and delete this message. |
From: Tatsuo I. <is...@po...> - 2014-02-06 02:08:29
|
> PGXC Hackers, > > What is the simplest way to tell if the server one has connected to is XC? Try to call pgxc_version()? `SHOW gtm_host`? Or is there something else to check, maybe something that doesn't throw an exception? What about this? SELECT count(*) from (SELECT has_function_privilege('%s', 'pgxc_version(text)', 'execute') WHERE EXISTS(SELECT * FROM pg_catalog.pg_proc AS p WHERE p.proname = 'pgxc_version')) AS s" Best regards, -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp |
From: David E. W. <da...@ju...> - 2014-02-06 01:28:43
|
On Feb 4, 2014, at 5:36 PM, Koichi Suzuki <koi...@gm...> wrote: > Because XC didn't change libpq at all, I cannot find explicit way if > you're connecting to PG or XC. Even psql binary from PG works with > XC. I'd suggest to test if pgxc_class, pgxc_node and pgxc_nodegroup > catalog is available, which are all XC specifyc. To avoid name > conflict (you can create table pgxc_class in PG), you can specify > pgxc_class oid value, which will be release-specific though. I don’t think I need to be *that* anal. If someone creates a table named pgxc_class in pg_catalog then the problem is theirs, IMHO. Thanks, David |
From: David E. W. <da...@ju...> - 2014-02-06 01:25:50
|
On Feb 4, 2014, at 5:56 PM, Michael Paquier <mic...@gm...> wrote: > How do you actually do for PG itself? Do you use PG_VERSION_NUM or similar? I don’t. Previously I did not have to distinguish Postgres from anything else. David |