On Wed, 25 Sep 2002, dima wrote:
> Date: Wed, 25 Sep 2002 18:56:28 +0400
> From: dima <[EMAIL PROTECTED]>
> To: pgsql-admin <[EMAIL PROTECTED]>
> Subject: [ADMIN] server error messages language
>
> can the server error messages language be changed somehow without
> remaking it from the sources?
Yoou could do the following:
SELECT list_of_all_columns_you_want_to_keep
INTO TABLE new_table
FROM old_table;
DROP TABLE old_table;
ALTER TABLE new_table RENAME TO old_table;
I saw this in Bruce Momjian'n book "PostgreSQL Introduction and Concepts".
Regards
Devinder Rajput
Stores Division Co
Sergio Pili writes:
> I nedd to compile it in SCO but the configure program abort.
Since your system didn't produce any output for the failed test, I can
only guess. Maybe you need to export LD_LIBRARY_PATH=/usr/local/lib to
allow it to find the readline libraries. Otherwise, try to compile th
dima writes:
> can the server error messages language be changed somehow without
> remaking it from the sources? the software catches english error
> messages for now & handles them well, but the freshly installed from rpm
> postgres returns error messages in russian & this causes software errors
On Wed, Sep 25, 2002 at 10:34:47AM -0400, Jodi Kanter wrote:
> Does version 7.2 of Postgresql allow us to remove a column from a
> table?
No.
> syntax wrong. I thought this was a feature that was going to be
> added??
Yes. 7.3.
A
--
Andrew Sullivan 204-4141 Yon
On Wed, Sep 25, 2002 at 09:14:36AM -0500, Devinder K Rajput wrote:
>
> # Syslog
> #
> #ifdef ENABLE_SYSLOG
> #syslog = 0 # range 0-2
> syslog = 2 # range 0-2
You've sent the logs to syslog, although some messages go to STDERR
anyway. If your syslog is not configured to do something with t
Hi all,
I am trying to setup logging. I have updated the postgresql.conf by making
the following changes:
#debug_level = 0 # range 0-16
debug_level = 2 # range 0-16
#debug_print_query = false
debug_print_query = true
...
# Syslog
#
#ifdef ENABLE_SYSLOG
#syslog = 0 # range 0-2
syslog = 2
The client needs to run on windows.
On Wed, 25 Sep 2002, Jean-Luc Lachance wrote:
> Why not use telnet???
>
> Laurette Cisneros wrote:
> >
> > I don't suppose anyone has this compiled for win2000 already as I don't
> > have MSVC++ available?
> >
> > L.
> > On Sat, 21 Sep 2002, Peter Eisentrau
Have you tried pg_dump. Command should look something like
pg_dump -t table_name db_name > output_file_name
Let me know if this works. Thanks.
Devinder Rajput
Stores Division Corporate Offices
Chicago, IL
(773) 442-6474
"Tom Lane" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
>
> Ah-hah! Thanks for posting that snippet. I dunno when it would have
> occurred to anyone to look for the cause of this message in backend
> shutdown, rather than backend startup ... but that was the
The following appeared in the log this am, while running "vacuumdb":
[13323] DEBUG: ReceiveSharedInvalidMessages: cache state reset
[25461] DEBUG: SendSharedInvalidMessage: SI buffer overflow
[13322] DEBUG: ReceiveSharedInvalidMessages: cache state reset
[13323] DEBUG: ReceiveSharedInvali
"Gaetano Mendola" <[EMAIL PROTECTED]> writes:
> Sep 24 13:49:59 pserver postgres[11625]: [1214176] DEBUG: proc_exit(0)
> Sep 24 13:49:59 pserver postgres[11625]: [1214177] DEBUG: shmem_exit(0)
> Sep 24 13:49:59 pserver postgres[11625]: [1214178] FATAL 1: LWLockAcquire:
> can't wait without a PR
Why not use telnet???
Laurette Cisneros wrote:
>
> I don't suppose anyone has this compiled for win2000 already as I don't
> have MSVC++ available?
>
> L.
> On Sat, 21 Sep 2002, Peter Eisentraut wrote:
>
> > Laurette Cisneros writes:
> >
> > > Is there a command line client to run sql against
Hi!
I nedd to compile it in SCO but the configure program abort.
Can you help me please?
Thank you!
Regards,
Sergio
--
OS version (from 'uname')
-
SCO Open Server 5.0.4
System = SCO_SV
Release = 3.2v5.0.4
KernelID = 97/05/07
Machine = Pent
can the server error messages language be changed somehow without
remaking it from the sources? the software catches english error
messages for now & handles them well, but the freshly installed from rpm
postgres returns error messages in russian & this causes software errors.
--
Not in 7.2, but it's in 7.3(beta).
HTH...
-Original Message-
From: Jodi Kanter [mailto:[EMAIL PROTECTED]]
Sent: Wed 9/25/2002 9:34 AM
To: Postgres Admin List
Cc:
Subject:[ADMIN] removing fields
Does version 7.2 of Postgresql allow us to remove a column from a table?
Does version 7.2 of Postgresql allow us to
remove a column from a table? It does not appear to be working but I may be
getting the syntax wrong. I thought this was a feature that was going to be
added??
Thanks
Jodi
___Jodi
L KanterBioInformatics Database Adminis
Thanks Phil- That was exactly what I needed.
A couple of notes that might help others-
My goal was to get all of the SQL statements from a JDBC front-end to be
logged as they are executed in the postgres.log file (and not in the
syslog.) Adding the following to my postgresql.conf did the job:
s
Hi all,
this morning I seen on my test linux box ( Postgres 7.2.2) the followin
lines in the logs:
Sep 24 13:49:59 pserver postgres[24943]: [1214174] DEBUG: BackendStartup:
forked pid=11625 socket=9
Sep 24 13:49:59 pserver postgres[11625]: [1214174] DEBUG: InitPostgres
Sep 24 13:49:59 pserver p
19 matches
Mail list logo
