Mailing lists [pgsql-hackers]

19 October 2009

• 01:09   Re: postgres 8.3.8 and Solaris 10_x86 64 bit problems? Andrew Chernow
• 02:24   foreign-key inference & join removal Robert Haas
• 04:01   Re: Reworks for Access Control facilities (r2363) KaiGai Kohei
• 04:22   Re: Reworks for Access Control facilities (r2363) KaiGai Kohei
• 04:40   Re: COPY enhancements Gokulakannan Somasundaram
• 06:28   Re: postgres 8.3.8 and Solaris 10_x86 64 bit problems? Zdenek Kotala
• 06:33   Re: postgres 8.3.8 and Solaris 10_x86 64 bit problems? Zdenek Kotala
• 07:02   Re: Reworks for Access Control facilities (r2363) Heikki Linnakangas
• 07:14   Re: Rejecting weak passwords Albe Laurenz
• 07:28   Re: Reworks for Access Control facilities (r2363) KaiGai Kohei
• 07:38   Re: Application name patch - v2 Peter Eisentraut
• 07:47   Re: Application name patch - v2 Dave Page
• 07:54   Re: Application name patch - v2 Pavel Stehule
• 08:09   Re: Application name patch - v2 Dave Page
• 08:11   Re: Application name patch - v2 Heikki Linnakangas
• 08:24   Re: Application name patch - v2 Pavel Stehule
• 08:30   Re: Application name patch - v2 Pavel Stehule
• 08:31   Re: Application name patch - v2 Dave Page
• 08:36   Re: Application name patch - v2 Pavel Stehule
• 08:43   Re: Application name patch - v2 Andrew Dunstan
• 08:44   Re: Application name patch - v2 Dave Page
• 08:57   Re: Application name patch - v2 Pavel Stehule
• 09:01   Re: Application name patch - v2 Pavel Stehule
• 09:03   Re: Application name patch - v2 Dave Page
• 09:12   Re: Application name patch - v2 Andrew Dunstan
• 09:22   Re: Application name patch - v2 Pavel Stehule
• 09:24   Re: Application name patch - v2 Pavel Stehule
• 09:31   Re: Application name patch - v2 Dave Page
• 09:42   Re: Application name patch - v2 Pavel Stehule
• 10:12   Re: Application name patch - v2 Dave Page
• 10:17   Re: Application name patch - v2 Dave Page
• 10:21   Re: Application name patch - v2 Peter Eisentraut
• 10:40   Re: Application name patch - v2 Dave Page
• 11:33   Re: Application name patch - v2 Pavel Stehule
• 11:35   Re: Rejecting weak passwords Peter Eisentraut
• 11:35   Re: Application name patch - v2 Pavel Stehule
• 11:39   Re: Application name patch - v2 Dave Page
• 11:51   Re: Rejecting weak passwords Peter Eisentraut
• 11:57   Re: Application name patch - v2 Pavel Stehule
• 12:00   Re: Application name patch - v2 Dave Page
• 12:07   Re: Deprecation daveg
• 12:14   Re: Application name patch - v2 daveg
• 12:31   Re: Application name patch - v2 Dimitri Fontaine
• 12:32   Re: Application name patch - v2 Pavel Stehule
• 12:55   Re: Rejecting weak passwords Albe Laurenz
• 13:03   Re: foreign-key inference & join removal Alex Brasetvik
• 13:13   Re: Application name patch - v2 Pavel Stehule
• 13:51   Re: postgres 8.3.8 and Solaris 10_x86 64 bit problems? Andrew Chernow
• 13:57   Re: foreign-key inference & join removal Robert Haas
• 14:07   Re: Rejecting weak passwords Robert Haas
• 14:17   Re: Application name patch - v2 David Fetter
• 14:30   Re: Writeable CTEs and side effects Marko Tiikkaja
• 14:31   Re: Rejecting weak passwords Tom Lane
• 14:33   Re: Application name patch - v2 Stephen Frost
• 14:37   Re: Application name patch - v2 Tom Lane
• 14:38   Re: Application name patch - v2 Stephen Frost
• 14:39   Re: Application name patch - v2 Dave Page
• 14:39   Re: Application name patch - v2 Tom Lane
• 14:41   Re: Application name patch - v2 Stephen Frost
• 14:43   Re: Application name patch - v2 Massa, Harald Armin
• 14:45   Re: Application name patch - v2 Dave Page
• 14:49   Re: Application name patch - v2 Tom Lane
• 14:54   Re: Controlling changes in plpgsql variable resolution Stephen Frost
• 15:02   Re: Application name patch - v2 Dave Page
• 15:10   Re: Application name patch - v2 Pavel Stehule
• 15:22   Re: COPY enhancements Alvaro Herrera
• 15:27   Re: Application name patch - v2 Stephen Frost
• 15:34   Re: COPY enhancements Robert Haas
• 15:36   Re: Controlling changes in plpgsql variable resolution Robert Haas
• 15:41   Re: Application name patch - v2 Robert Haas
• 15:50   Re: Writeable CTEs and side effects Tom Lane
• 15:54   Re: Application name patch - v2 Kevin Grittner
• 15:56   Re: ALTER TABLE SET STATISTICS requires AccessExclusiveLock Alvaro Herrera
• 16:01   Re: ALTER TABLE SET STATISTICS requires AccessExclusiveLock Simon Riggs
• 16:08   Re: Rejecting weak passwords Peter Eisentraut
• 16:08   Re: Application name patch - v2 Kevin Grittner
• 16:12   Re: Rejecting weak passwords Tom Lane
• 16:23   Re: Rejecting weak passwords Alvaro Herrera
• 16:25   Re: Controlling changes in plpgsql variable resolution David E. Wheeler
• 16:27   Re: Controlling changes in plpgsql variable resolution David E. Wheeler
• 16:29   Re: Controlling changes in plpgsql variable resolution Stephen Frost
• 16:37   Re: Rejecting weak passwords Andrew Dunstan
• 16:38   Re: Rejecting weak passwords Tom Lane
• 16:38   Re: Application name patch - v2 Pavel Stehule
• 16:42   Re: Controlling changes in plpgsql variable resolution David E. Wheeler
• 16:49   Re: Controlling changes in plpgsql variable resolution Tom Lane
• 16:53   Re: Controlling changes in plpgsql variable resolution David E. Wheeler
• 16:55   Re: Scaling up deferred unique checks and the after trigger queue Dean Rasheed
• 17:02   Re: Scaling up deferred unique checks and the after trigger queue Robert Haas
• 17:05   Re: Controlling changes in plpgsql variable resolution Kevin Grittner
• 17:07   Re: Scaling up deferred unique checks and the after trigger queue Dean Rasheed
• 17:17   Re: Rejecting weak passwords Tom Lane
• 17:18   Re: Controlling changes in plpgsql variable resolution Pavel Stehule
• 17:45   Re: Controlling changes in plpgsql variable resolution Merlin Moncure
• 17:47   Re: Controlling changes in plpgsql variable resolution Robert Haas
• 17:50   Re: postgres 8.3.8 and Solaris 10_x86 64 bit problems? u235sentinel
• 17:51   Re: Controlling changes in plpgsql variable resolution Tom Lane
• 17:57   Re: Controlling changes in plpgsql variable resolution Robert Haas
• 18:09   Re: Controlling changes in plpgsql variable resolution Tom Lane
• 18:09   Re: Controlling changes in plpgsql variable resolution Kevin Grittner
• 18:14   Re: Controlling changes in plpgsql variable resolution Andrew Dunstan
• 18:14   Re: postgres 8.3.8 and Solaris 10_x86 64 bit problems? Andrew Chernow
• 18:14   Re: Controlling changes in plpgsql variable resolution Tom Lane
• 18:50   Re: Controlling changes in plpgsql variable resolution Tom Lane
• 18:55   Re: Controlling changes in plpgsql variable resolution David E. Wheeler
• 19:06   Re: Controlling changes in plpgsql variable resolution Tom Lane
• 19:07   Re: postgres 8.3.8 and Solaris 10_x86 64 bit problems? Zdenek Kotala
• 19:13   Re: Controlling changes in plpgsql variable resolution Eric B. Ridge
• 19:13   Re: Controlling changes in plpgsql variable resolution David E. Wheeler
• 19:15   Re: Controlling changes in plpgsql variable resolution Tom Lane
• 19:23   Re: Controlling changes in plpgsql variable resolution Tom Lane
• 19:46   Re: Controlling changes in plpgsql variable resolution Tom Lane
• 19:53   Re: Controlling changes in plpgsql variable resolution David E. Wheeler
• 20:35   Re: Application name patch - v2 Magnus Hagander
• 20:40   Re: LATERAL Greg Stark
• 21:01   Re: Controlling changes in plpgsql variable resolution Eric B. Ridge
• 21:08   Could postgres be much cleaner if a future release skipped backward compatibility? Ron Mayer
• 21:10   per table random-page-cost? marcin mank
• 21:14   Re: per table random-page-cost? Robert Haas
• 21:27   Re: per table random-page-cost? Greg Stark
• 21:55   Re: per table random-page-cost? Kevin Grittner
• 22:18   Re: per table random-page-cost? marcin mank
• 22:19   Re: per table random-page-cost? marcin mank
• 22:26   Re: LATERAL Tom Lane
• 22:33   Re: per table random-page-cost? Tom Lane
• 22:38   Re: LATERAL Andrew Gierth
• 22:45   Re: Could postgres be much cleaner if a future release skipped backward compatibility? Tom Lane
• 22:45   Re: per table random-page-cost? Andrew Dunstan
• 23:04   Re: per table random-page-cost? marcin mank
• 23:21   Re: per table random-page-cost? Tom Lane
• 23:29   Re: per table random-page-cost? Greg Stark
• 23:39   Re: per table random-page-cost? Greg Stark