HackorumHackorum
Menu
TopicsSearchStatisticsReportsHelpSign inRegister
PostgreSQL Hackers Archive
TopicsSearchReports
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: Fix coerce_to_target_type for coerce_type's klugy handling of CO
pgsql: Fix coerce_to_target_type for coerce_type's klugy handling of CO
Tom LaneTom LaneTom LaneTom Lane
0 replies
Jan 02, 2012
comitters
0 replies
Jan 02, 2012
Tom Lane
1
Tom Lane
Tom Lane
pgsql: Fix coerce_to_target_type for coerce_type's klugy handling of CO
pgsql: Fix coerce_to_target_type for coerce_type's klugy handling of CO
Tom LaneTom LaneTom LaneTom Lane
0 replies
Jan 02, 2012
comitters
0 replies
Jan 02, 2012
Tom Lane
1
Tom Lane
Tom Lane
pgsql: Use LWSYNC in place of SYNC/ISYNC in PPC spinlocks, where possib
pgsql: Use LWSYNC in place of SYNC/ISYNC in PPC spinlocks, where possib
Tom LaneTom LaneTom LaneTom Lane
0 replies
Jan 02, 2012
comitters
0 replies
Jan 02, 2012
Tom Lane
1
Tom Lane
Tom Lane
pgsql: Use 4-byte slock_t on both PPC and PPC64.
pgsql: Use 4-byte slock_t on both PPC and PPC64.
Tom LaneTom LaneTom LaneTom Lane
0 replies
Jan 02, 2012
comitters
0 replies
Jan 02, 2012
Tom Lane
1
Tom Lane
Tom Lane
pgsql: Use mutex hint bit in PPC LWARX instructions, where possible.
pgsql: Use mutex hint bit in PPC LWARX instructions, where possible.
Tom LaneTom LaneTom LaneTom Lane
0 replies
Jan 02, 2012
comitters
0 replies
Jan 02, 2012
Tom Lane
1
Tom Lane
Tom Lane