• Text Size: Normal / Large
• Donate
• Contact

Section Navigation

• Community
• Contributors
• Mailing Lists
  • Subscribe
  • User lists
  • Developer lists
    • pgsql-committers
    • pgsql-hackers
    • pgsql-patches
    • pgsql-www
  • Regional lists
  • Project lists
  • User groups
  • Inactive lists
• IRC
• Featured Users
• International Sites
• Propaganda
• Resources
• Weekly News
• Community login
  • Profile
  • Lost password

Re: lo function changed in PostgreSQL 8.1.1

• From: "Premsun Choltanwanich" <Premsun(at)nsasia(dot)co(dot)th>
• To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
• Cc: "Richard Huxton" <dev(at)archonet(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
• Subject: Re: lo function changed in PostgreSQL 8.1.1
• Date: Tue, 20 Dec 2005 11:35:29 +0700
• Message-id: <43A7EC77(dot)C5F7(dot)004C(dot)0(at)nsasia(dot)co(dot)th>

• References:
  • lo function changed in PostgreSQL 8.1.1
    • From: Premsun Choltanwanich
  • Re: lo function changed in PostgreSQL 8.1.1
    • From: Richard Huxton
  • Re: lo function changed in PostgreSQL 8.1.1
    • From: Premsun Choltanwanich
  • Re: lo function changed in PostgreSQL 8.1.1
    • From: Tom Lane

• Prev by Date: Re: localization problem (and solution)
• Next by Date: Re: Lock issue when trying to vacuum db
• Previous by thread: Re: lo function changed in PostgreSQL 8.1.1
• Next by thread: ERROR: could not access status of transaction on postgresql 8.0.3
• Indexes:
  • Main
  • Thread