Search Results - Hackorum

Topic	Mailing Lists	Activity	Participants
Run pgindent now?hackers Run pgindent now? Tom LaneBruce Momjian 83 replies Jun 10, 2015	hackers	83 replies Jun 10, 2015	+7 10 Tom Lane Bruce Momjian Alvaro Herrera Andres Freund Robert Haas Andrew Dunstan Peter Eisentraut Magnus Hagander Noah Misch Stephen Frost
initdb -S versus superuser check and Windows restricted modehackers initdb -S versus superuser check and Windows restricted mode Tom LaneMichael Paquier 1 reply May 30, 2015	hackers	1 reply May 30, 2015	2 Tom Lane Michael Paquier
pgsql: Adjust initdb to also not consider fsync'ing failures fatal.comitters pgsql: Adjust initdb to also not consider fsync'ing failures fatal. Tom LanePeter Eisentraut 3 replies May 30, 2015	comitters	3 replies May 30, 2015	2 Tom Lane Peter Eisentraut
pgsql: Remove special cases for ETXTBSY from new fsync'ing logic.comitters pgsql: Remove special cases for ETXTBSY from new fsync'ing logic. Tom LaneAndres Freund 1 reply May 29, 2015	comitters	1 reply May 29, 2015	2 Tom Lane Andres Freund
pgsql: initdb -S should now have an explicit check that $PGDATA is valicomitters pgsql: initdb -S should now have an explicit check that $PGDATA is vali Tom LaneTom Lane 0 replies May 29, 2015	comitters	0 replies May 29, 2015	1 Tom Lane
pgsql: initdb -S should now have an explicit check that $PGDATA is valicomitters pgsql: initdb -S should now have an explicit check that $PGDATA is vali Tom LaneTom Lane 0 replies May 29, 2015	comitters	0 replies May 29, 2015	1 Tom Lane
pgsql: initdb -S should now have an explicit check that $PGDATA is valicomitters pgsql: initdb -S should now have an explicit check that $PGDATA is vali Tom LaneTom Lane 0 replies May 29, 2015	comitters	0 replies May 29, 2015	1 Tom Lane
pgsql: Remove special cases for ETXTBSY from new fsync'ing logic.comitters pgsql: Remove special cases for ETXTBSY from new fsync'ing logic. Tom LaneTom Lane 0 replies May 29, 2015	comitters	0 replies May 29, 2015	1 Tom Lane
pgsql: Remove special cases for ETXTBSY from new fsync'ing logic.comitters pgsql: Remove special cases for ETXTBSY from new fsync'ing logic. Tom LaneTom Lane 0 replies May 29, 2015	comitters	0 replies May 29, 2015	1 Tom Lane
pgsql: Remove special cases for ETXTBSY from new fsync'ing logic.comitters pgsql: Remove special cases for ETXTBSY from new fsync'ing logic. Tom LaneTom Lane 0 replies May 29, 2015	comitters	0 replies May 29, 2015	1 Tom Lane
pgsql: Remove special cases for ETXTBSY from new fsync'ing logic.comitters pgsql: Remove special cases for ETXTBSY from new fsync'ing logic. Tom LaneTom Lane 0 replies May 29, 2015	comitters	0 replies May 29, 2015	1 Tom Lane
pgsql: Remove special cases for ETXTBSY from new fsync'ing logic.comitters pgsql: Remove special cases for ETXTBSY from new fsync'ing logic. Tom LaneTom Lane 0 replies May 29, 2015	comitters	0 replies May 29, 2015	1 Tom Lane
pgsql: Check that all aliases of a built-in function have same leakproocomitters pgsql: Check that all aliases of a built-in function have same leakproo Tom LaneTom Lane 0 replies May 29, 2015	comitters	0 replies May 29, 2015	1 Tom Lane
pgsql: Adjust initdb to also not consider fsync'ing failures fatal.comitters pgsql: Adjust initdb to also not consider fsync'ing failures fatal. Tom LaneTom Lane 0 replies May 29, 2015	comitters	0 replies May 29, 2015	1 Tom Lane
pgsql: Adjust initdb to also not consider fsync'ing failures fatal.comitters pgsql: Adjust initdb to also not consider fsync'ing failures fatal. Tom LaneTom Lane 0 replies May 29, 2015	comitters	0 replies May 29, 2015	1 Tom Lane
pgsql: Revert exporting of internal GUC variable "data_directory".comitters pgsql: Revert exporting of internal GUC variable "data_directory". Tom LaneTom Lane 0 replies May 29, 2015	comitters	0 replies May 29, 2015	1 Tom Lane
proleakproof vs opr_sanity testhackers proleakproof vs opr_sanity test Tom LaneMichael Paquier 1 reply May 29, 2015	hackers	1 reply May 29, 2015	2 Tom Lane Michael Paquier
hstore_plpython regression test does not work on Python 3hackers hstore_plpython regression test does not work on Python 3 Tom LaneOskari Saarenmaa 6 replies May 29, 2015	hackers	6 replies May 29, 2015	2 Tom Lane Peter Eisentraut
pgsql: Fix fsync-at-startup code to not treat errors as fatal.comitters pgsql: Fix fsync-at-startup code to not treat errors as fatal. Tom LaneTom Lane 0 replies May 28, 2015	comitters	0 replies May 28, 2015	1 Tom Lane
pgsql: Fix fsync-at-startup code to not treat errors as fatal.comitters pgsql: Fix fsync-at-startup code to not treat errors as fatal. Tom LaneTom Lane 0 replies May 28, 2015	comitters	0 replies May 28, 2015	1 Tom Lane
pgsql: Fix fsync-at-startup code to not treat errors as fatal.comitters pgsql: Fix fsync-at-startup code to not treat errors as fatal. Tom LaneTom Lane 0 replies May 28, 2015	comitters	0 replies May 28, 2015	1 Tom Lane
pgsql: Fix fsync-at-startup code to not treat errors as fatal.comitters pgsql: Fix fsync-at-startup code to not treat errors as fatal. Tom LaneTom Lane 0 replies May 28, 2015	comitters	0 replies May 28, 2015	1 Tom Lane
pgsql: Fix fsync-at-startup code to not treat errors as fatal.comitters pgsql: Fix fsync-at-startup code to not treat errors as fatal. Tom LaneTom Lane 0 replies May 28, 2015	comitters	0 replies May 28, 2015	1 Tom Lane
pgsql: Fix fsync-at-startup code to not treat errors as fatal.comitters pgsql: Fix fsync-at-startup code to not treat errors as fatal. Tom LaneTom Lane 0 replies May 28, 2015	comitters	0 replies May 28, 2015	1 Tom Lane
About that re-release ...hackers About that re-release ... Tom LaneMarco Atzeri 7 replies May 28, 2015	hackers	7 replies May 28, 2015	3 Robert Haas Tom Lane Josh Berkus

Loading more results...

Mailing Lists

Saved searches