On Dec 16, 2007 6:11 PM, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Sun, 16 Dec 2007 17:55:55 -0600
> "Scott Marlowe" <[EMAIL PROTECTED]> wrote:
>
> > On Dec 14, 2007 1:33 AM, Ow Mun Heng <[EMAIL PROTECTED]> wrote:
> > > I kept looking at the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 16 Dec 2007 17:55:55 -0600
"Scott Marlowe" <[EMAIL PROTECTED]> wrote:
> On Dec 14, 2007 1:33 AM, Ow Mun Heng <[EMAIL PROTECTED]> wrote:
> > I kept looking at the io columns and didn't even think of the swap
> > partition. It's true that it's m
On Dec 14, 2007 1:33 AM, Ow Mun Heng <[EMAIL PROTECTED]> wrote:
> I kept looking at the io columns and didn't even think of the swap
> partition. It's true that it's moving quite erratically but I won't say
> that it's really thrashing.
>
> total used free sharedbuf
Tom Lane wrote:
Colin Wetherbee <[EMAIL PROTECTED]> writes:
Let's say I have a users table that holds about 15 columns of data about
each user.
If I write one Perl sub for each operation on the table (e.g. one that
gets the username and password hash, another that gets the last name and
firs
Colin Wetherbee <[EMAIL PROTECTED]> writes:
> Let's say I have a users table that holds about 15 columns of data about
> each user.
> If I write one Perl sub for each operation on the table (e.g. one that
> gets the username and password hash, another that gets the last name and
> first name, e
Greetings.
I am working on a PostgreSQL-backed mod_perl web application that's just
in its infancy.
Let's say I have a users table that holds about 15 columns of data about
each user.
If I write one Perl sub for each operation on the table (e.g. one that
gets the username and password hash
Bruce Momjian <[EMAIL PROTECTED]> writes:
> We used to have the C defined MAKE_EXPIRED_TUPLES_VISIBLE that would
> make deleted rows visible, but it seems it was removed in this commit as
> part of a restructuring:
It was removed because it was utterly useless.
regards, to
Joshua D. Drake wrote:
> Don't put this one on me :). This is a community thing. AndrewS reply
> aside, if you review the "will" of the community on this you will see
> that top posting is frowned upon.
>
> I will be the first to step up and pick a fight when I think the
> community is being dumb
Howard Cole wrote:
>
> Which you can do, no? I thought pg_ctl's kill option was invented
> specifically to make this less painful on Windows.
> > I shall look into the pg_ctl options to see if the kill option does
> > what taskill cannot (thanks for the heads up on that)
> >
> Using
>
