Re: [DOCS] [BUGS] issue about information_schema REFERENTIAL_CONSTRAINTS

[Bruce Momjian]

Fabien COELHO wrote:
> 
> >> Is that the direction we want to go, or would it be better to factor
> >> the information out into a separate page about compatibility gotchas?
> >
> > It would probably be better to explain globally applicable issues in a
> > separate section.
> 
> I agree that a general caveat is better, together with a one line 
> reference in the documentation of each table with an issue.

Oh, I just noticed this.  Can you give me a list of information_schema
tables that have this issue?  I am only aware of
referential_constraints.

-- 
  Bruce Momjian  http://momjian.us
  EnterpriseDB http://enterprisedb.com

  + It's impossible for everything to be true. +

-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

Re: [DOCS] Terms.

[Bruce Momjian]

Alvaro Herrera wrote:
> Excerpts from Dmitriy Igrishin's message of lun sep 20 15:52:43 -0400 2010:
> > Hey Bruce,
> > 
> > Its interesting indeed, because I always wanted to know why libpq
> > named "libpq". Thanks!
> > But I wrote not about libpq functions, I just wanted to say about
> > unnecessary (IMO) redundancy - the combinations of terms "backend server"
> > seems to me inaccuracy.
> 
> could be, but we're already using that term elsewhere.  Maybe we should
> consistently use some other term.
> 
> 
> $ git grep 'backend server'
> 
> doc/src/sgml/libpq.sgml:  backend server and to receive the results of these 
> queries.
> doc/src/sgml/libpq.sgml:   PostgreSQL backend 
> server.  An
> doc/src/sgml/libpq.sgml:   server processin libpq of 
> the backend server
> doc/src/sgml/problems.sgml:   Here program refers to any 
> executable, not only the backend server.
> doc/src/sgml/problems.sgml:   are specifically talking about the backend 
> server, mention that, do not
> doc/src/sgml/problems.sgml:   backend server process is quite different from 
> crash of the parent
> doc/src/sgml/query.sgml:backend server machine, not the client, since the 
> backend server
> doc/src/sgml/ref/pg_ctl-ref.sgml:   backend server ( linkend="app-postgres">), or displaying the
> src/backend/libpq/pqsignal.c: * the frontend commands as well as the backend 
> server.
> src/backend/main/main.c:printf(_("  -T  send SIGSTOP to all 
> backend servers if one dies\n"));
> src/backend/po/de.po:msgid "  -T  send SIGSTOP to all backend 
> servers if one dies\n"
> src/backend/po/es.po:msgid "  -T  send SIGSTOP to all backend 
> servers if one dies\n"
> src/backend/po/fr.po:msgid "  -T  send SIGSTOP to all backend 
> servers if one dies\n"
> src/backend/po/ja.po:msgid "  -T  send SIGSTOP to all backend 
> servers if one dies\n"
> src/backend/po/pt_BR.po:msgid "  -T  send SIGSTOP to all backend 
> servers if one dies\n"
> src/backend/po/tr.po:msgid "  -T  send SIGSTOP to all backend 
> servers if one dies\n"
> src/bin/psql/settings.h:int sversion;   /* backend server 
> version */
> src/test/examples/testlibpq4.c: pghost = NULL;  /* host name of 
> the backend server */
> src/test/examples/testlibpq4.c: pgport = NULL;  /* port of the 
> backend server */
> src/test/examples/testlibpq4.c: pgtty = NULL;   /* debugging tty 
> for the backend server */

Any ideas on this?  Is "backend" better than "backend server"?

-- 
  Bruce Momjian  http://momjian.us
  EnterpriseDB http://enterprisedb.com

  + It's impossible for everything to be true. +

-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs