Update URL for pgtclng project.
Thom Brown
Branch
--
REL8_4_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/34684cee64652ed1bc66f02f41c47196bfce1441
Modified Files
--
doc/src/sgml/external-projects.sgml |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
Update URL for pgtclng project.
Thom Brown
Branch
--
REL9_1_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/63d8636c50f2ca053aa6a214340bb322bc5687d5
Modified Files
--
doc/src/sgml/external-projects.sgml |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
Update URL for pgtclng project.
Thom Brown
Branch
--
REL9_0_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/f42a4c01f4bae27a06330ab235adb6533ca4ecd9
Modified Files
--
doc/src/sgml/external-projects.sgml |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
Update URL for pgtclng project.
Thom Brown
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/d75829a682fdf832fe9d044b28be597d3f058ec8
Modified Files
--
doc/src/sgml/external-projects.sgml |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
--
Sen
Update URL for pgtclng project.
Thom Brown
Branch
--
REL8_3_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/1cba1142b3e3b09866eeb68b939136bea30e2695
Modified Files
--
doc/src/sgml/external-projects.sgml |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
Fix misleading output from gin_desc().
XLOG_GIN_UPDATE_META_PAGE and XLOG_GIN_DELETE_LISTPAGE records were printed
with a list link field labeled as "blkno", which was confusing, especially
when the link was empty (InvalidBlockNumber). Print the metapage block
number instead, since that's what's
Fix misleading output from gin_desc().
XLOG_GIN_UPDATE_META_PAGE and XLOG_GIN_DELETE_LISTPAGE records were printed
with a list link field labeled as "blkno", which was confusing, especially
when the link was empty (InvalidBlockNumber). Print the metapage block
number instead, since that's what's
Fix misleading output from gin_desc().
XLOG_GIN_UPDATE_META_PAGE and XLOG_GIN_DELETE_LISTPAGE records were printed
with a list link field labeled as "blkno", which was confusing, especially
when the link was empty (InvalidBlockNumber). Print the metapage block
number instead, since that's what's
Fix misleading output from gin_desc().
XLOG_GIN_UPDATE_META_PAGE and XLOG_GIN_DELETE_LISTPAGE records were printed
with a list link field labeled as "blkno", which was confusing, especially
when the link was empty (InvalidBlockNumber). Print the metapage block
number instead, since that's what's
Fix broken comparetup_datum code.
Commit 337b6f5ecf05b21b5e997986884d097d60e4e3d0 contained the entirely
fanciful assumption that it had made comparetup_datum unreachable.
Reported and patched by Takashi Yamamoto.
Fix up some not terribly accurate/useful comments from that commit, too.
Branch
--
Fix some typos in the documentation
Thom Brown
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/6c41948c39288139cd9a592466cd373b6868bb55
Modified Files
--
doc/src/sgml/ref/pg_receivexlog.sgml |2 +-
doc/src/sgml/reference.sgml |2 +-
2 file
Correct various system catalog/view definitions in the documentation
Thom Brown
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/25028a27c828b8d31a85064f230113a42c0fea81
Modified Files
--
doc/src/sgml/catalogs.sgml | 41 +
Dept of second thoughts: improve the API for AnalyzeForeignTable.
If we make the initially-called function return the table physical-size
estimate, acquire_inherited_sample_rows will be able to use that to
allocate numbers of samples among child tables, when the day comes that
we want to support f
Allow statistics to be collected for foreign tables.
ANALYZE now accepts foreign tables and allows the table's FDW to control
how the sample rows are collected. (But only manual ANALYZEs will touch
foreign tables, for the moment, since among other things it's not very
clear how to handle remote p
(2012/04/06 18:27), Simon Riggs wrote:
> Add DROP INDEX CONCURRENTLY [IF EXISTS], uses ShareUpdateExclusiveLock
> src/backend/catalog/index.c| 139 ++-
I got a compiler warning "set but not used" about newly added variable
indexlocktag. Is it ok?
Regards,
Add DROP INDEX CONCURRENTLY [IF EXISTS], uses ShareUpdateExclusiveLock
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/8cb53654dbdb4c386369eb988062d0bbb6de725e
Modified Files
--
doc/src/sgml/ref/drop_index.sgml | 25 +-
src/backend/catalog/
16 matches
Mail list logo