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
(11) |
2
(7) |
3
(6) |
4
|
5
|
6
(1) |
7
(2) |
8
(2) |
9
(6) |
10
(2) |
11
|
12
(1) |
13
(6) |
14
(5) |
15
(4) |
16
(5) |
17
(4) |
18
|
19
|
20
(1) |
21
(3) |
22
(2) |
23
(1) |
24
|
25
|
26
|
27
(5) |
28
|
29
|
30
|
31
|
|
From: xiong w. <wan...@gm...> - 2010-12-08 10:33:46
|
Dears, steps: postgres=# create sequence seq start with 1; CREATE SEQUENCE postgres=# create table t(a int default nextval('seq'), b int); ERROR: Could not commit (or autocommit) data node connection datanode log as follows: LOG: statement: create table t(a int default nextval('seq'), b int); ERROR: relation "seq" does not exist When I checked the source code, I found sequence can't be created on datanodes. Could you explain why? Regards, Benny |
From: Michael P. <mic...@gm...> - 2010-12-08 07:24:49
|
Continuing on the modifications for 2PC, I finished a patch extending 2PC file and 2PC xact data protocol. With the patch attached, 2PC data contains the following information: - if the 2PC is implicit or explicit - if the transaction prepared contained DDL or not (if yes, it means that the transaction has also been prepared on Coordinators) - the coordinator number from where the 2PC has been issued - the list of nodes where the transaction has been prepared. In case of a transaction that prepared only on Coordinators, the list of nodes is set to "n" (case of sequence transactions) 2PC information below is sent down to nodes when an implicit or explicit prepare is made, and only on the necessary nodes. The patch also contains an extension of the view pg_prepared_xacts to be able to get from catalog table the extended 2PC information as well as the usual 2PC data. If you want to make tests, you have to apply first on HEAD implicit2pc6.patch and then apply implicit2pc6_extend_pg_prepared_xacts.patch. I forgot to say that, as pg_prepared_xacts is a catalog view, you have to connect to a node directly to get the 2PC information. The information could also be obtained with EXECUTE DIRECT but currently this functionality is broken. In the test I did, of course I checked if the views were OK, but also I checked that recovery of prepared transactions was properly done. If you want to try, kill a postgres process with SIGQUIT (kill -3) and relaunch it. 2PC data will recover from the 2PC files correctly. You can check by launching "select * from pg_prepared_xacts;" before and after stopping the postgres instance. Regards, Michael -- Michael Paquier http://michaelpq.users.sourceforge.net |