HackorumHackorum
Menu
TopicsCISearchStatisticsReportsHelpSign inRegister
PostgreSQL Hackers Archive
TopicsCISearchReports
Sign inRegister
StatisticsHelpSign inRegister
Search syntax help

Mailing Lists

  • All lists
  • bugs
  • comitters
  • docs
  • general
  • hackers
  • patches

Saved searches

Global
  • No contributor/committer replies
  • Patch, no replies
TopicMailing ListsActivityParticipants
pgsql: Remove extremely old, incomplete, broken example code.comitters
pgsql: Remove extremely old, incomplete, broken example code.
Tom LaneTom LaneTom LaneTom Lane
0 replies
Jun 05, 2006
comitters
0 replies
Jun 05, 2006
Tom Lane
1
Tom Lane
Tom Lane
pgsql: While making the seq_page_cost changes, I was struck by the factcomitters
pgsql: While making the seq_page_cost changes, I was struck by the fact
Tom LaneTom LaneTom LaneTom Lane
0 replies
Jun 05, 2006
comitters
0 replies
Jun 05, 2006
Tom Lane
1
Tom Lane
Tom Lane
pgsql: Increase the default value of cpu_index_tuple_cost from 0.001 tocomitters
pgsql: Increase the default value of cpu_index_tuple_cost from 0.001 to
Tom LaneTom LaneTom LaneTom Lane
0 replies
Jun 05, 2006
comitters
0 replies
Jun 05, 2006
Tom Lane
1
Tom Lane
Tom Lane
pgsql: Add a GUC parameter seq_page_cost, and use that everywhere wecomitters
pgsql: Add a GUC parameter seq_page_cost, and use that everywhere we
Tom LaneTom LaneTom LaneTom Lane
0 replies
Jun 05, 2006
comitters
0 replies
Jun 05, 2006
Tom Lane
1
Tom Lane
Tom Lane