Re: perform.sgml update - Mailing list pgsql-patches

From Bruce Momjian
Subject Re: perform.sgml update
Date
Msg-id 200306230609.h5N69Qt04983@candle.pha.pa.us
Whole thread Raw
In response to perform.sgml update  ("Greg Sabino Mullane" <greg@turnstep.com>)
List pgsql-patches
Your patch has been added to the PostgreSQL unapplied patches list at:

    http://momjian.postgresql.org/cgi-bin/pgpatches

I will try to apply it within the next 48 hours.

---------------------------------------------------------------------------


Greg Sabino Mullane wrote:
[ There is text before PGP section. ]
>
[ PGP not available, raw data follows ]
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> NotDashEscaped: You need GnuPG to verify this message
>
>
> Small patch to link to the proper place in the "runtime" file,
> and to add the "schemaname" column to the description of the
> pg_stats view.
>
>
> --
> Greg Sabino Mullane greg@turnstep.com
> PGP Key: 0x14964AC8 200306111031
>
>
>
> Index: perform.sgml
> ===================================================================
> RCS file: /projects/cvsroot/pgsql-server/doc/src/sgml/perform.sgml,v
> retrieving revision 1.28
> diff -c -r1.28 perform.sgml
> *** perform.sgml    25 Mar 2003 16:15:37 -0000    1.28
> --- perform.sgml    11 Jun 2003 14:22:02 -0000
> ***************
> *** 66,72 ****
>       estimates are converted into disk-page units using some
>       fairly arbitrary fudge factors. If you want to experiment with these
>       factors, see the list of run-time configuration parameters in
> !     <xref linkend="runtime-config">.)
>      </para>
>
>      <para>
> --- 66,72 ----
>       estimates are converted into disk-page units using some
>       fairly arbitrary fudge factors. If you want to experiment with these
>       factors, see the list of run-time configuration parameters in
> !     <xref linkend="runtime-config-optimizer">.)
>      </para>
>
>      <para>
> ***************
> *** 435,440 ****
> --- 435,446 ----
>       </thead>
>
>       <tbody>
> +      <row>
> +       <entry><literal>schemaname</literal></entry>
> +       <entry><type>name</type></entry>
> +       <entry>Name of the schema containing the table.</entry>
> +      </row>
> +
>        <row>
>         <entry><literal>tablename</literal></entry>
>         <entry><type>name</type></entry>
>
>
>
>
>
> -----BEGIN PGP SIGNATURE-----
> Comment: http://www.turnstep.com/pgp.html
>
> iD8DBQE+5z3ovJuQZxSWSsgRAlIhAJ4mOgsrKa1xQXiMxTWWawPsGrnPjgCg3BLs
> fw61yiB/4rfQotCO4MIvI4Y=
> =YoCD
> -----END PGP SIGNATURE-----
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
>
[ Decrypting message... End of raw data. ]

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

pgsql-patches by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: UPDATE ... SET = DEFAULT
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] MARKED_FOR_UPDATE && XMAX_COMMITTED == XMAX_INVALID ?