subscribe
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
On Wed, Mar 13, 2002 at 05:23:30PM -0800, Gill, Jeffrey L wrote:
Specs: Server RedHat 7.1 2.4.2-2 kernal everything build with Interchange
4.8
I am learning Linux and Postgresql from scratch.
1. Can someone point me to or explain any linux kernal optimizations for
redhat that can
I'm using Solaris 5.7 on an ultra 5.
I've attempted to build postgre 7.2 and I still get the same message.
accept is decalred as:
#ifdef __STDC__
extern int accept(int, struct sockaddr *, Psocklen_t);
extern int bind(int, const struct sockaddr *, socklen_t);
extern int connect(int, const
In postgresql.conf:
# Syslog
# requires ENABLE_SYSLOG
How to do it?
My OS is FreeBSD4.5
I installed Postgres-7.2
Urgent!
Thanks!
Jie Liang
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
Jie Liang wrote:
In postgresql.conf:
# Syslog
# requires ENABLE_SYSLOG
How to do it?
My OS is FreeBSD4.5
I installed Postgres-7.2
Urgent!
I think you need to make sure that PostgreSQL was built with
--enable-syslog during configure.
Joe
---(end
I did, it didn't work.
Jie Liang
-Original Message-
From: Joe Conway [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 14, 2002 10:49 AM
To: Jie Liang
Cc: '[EMAIL PROTECTED]'; pgsql-sql
Subject: Re: [ADMIN] Syslog
Jie Liang wrote:
In postgresql.conf:
# Syslog
# requires
On 14 Mar 2002 at 10:48, Joe Conway wrote:
Jie Liang wrote:
In postgresql.conf:
# Syslog
# requires ENABLE_SYSLOG
How to do it?
My OS is FreeBSD4.5
I installed Postgres-7.2
Urgent!
Try not to think that your message is more important than any other. It's
not like
Jie Liang wrote:
I did, it didn't work.
Jie Liang
Works for me. Did you change postgresql.conf? Here's what mine looks like.
#
# Syslog
#
# requires ENABLE_SYSLOG
syslog = 1 # range 0-2
syslog_facility = 'LOCAL0'
syslog_ident = 'postgres'
From the online docs:
I did everything as you did, however, when start the postmaster,
I got following:
FATAL 1:'syslog' is not a valid option name.
Jie
-Original Message-
From: Joe Conway [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 14, 2002 11:27 AM
To: Jie Liang
Cc: '[EMAIL PROTECTED]';
Hi,
I always have questions on sql tunning, here is the one:
gtld_analysis=# \d gtld_owner
Table gtld_owner
Attribute| Type | Modifier
++
owner_name | character varying(100) |
netblock_start
Haven't get any reply yet. I like to post more information:
select * from pg_statistic where starelid=(select oid from
pg_class where relname='gtld_owner');
starelid | staattnum | stanullfrac | stawidth | stadistinct | stakind1 |
stakind2 | stakind3 | stakind4 | staop1 | staop2 | staop3 |
On Thu, 2002-03-14 at 20:13, Jie Liang wrote:
I did everything as you did, however, when start the postmaster,
I got following:
FATAL 1: 'syslog' is not a valid option name.
Then you haven't configured postgresql with --enable-syslog. (That
message comes from
How do you separate the postgresql database files in InterChange
from the rest of the application?
What is the command syntax and what files need to be modified that
call and point to the database? I am researching DSN...
My goal is to separate InterChange so it can exist on three
On Thu, 14 Mar 2002, Zhang, Anna wrote:
gtld_analysis=# explain SELECT NETBLOCK_START
gtld_analysis-# FROM GTLD_OWNER
gtld_analysis-# WHERE NETBLOCK_START = -2147483648;
You might want to try the same query but with the constant integer
enclosed in single quotes. I find that (at least for
Tycho's suggestion worked great.
Is this a bug in postgres, and is Tycho's suggestion a workaround, or is it
supposed to be like this?
--
Mike Schiraldi
VeriSign Applied Research
smime.p7s
Description: application/pkcs7-signature
Tycho,You saved us!
This problem really bothered us for a while, now we know why we had hard
time before. But I think it is a postgres bug. Thanks a lot!
Anna Zhang
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 14, 2002 5:29 PM
To: Zhang,
Our replication system appears to have crashed and left locks on all the
tables. How can I unlock the tables for writing again?
I have tried dumping the data and re-importing into a fresh database, but
the locks appear to be stored with the dump.
Terry Cox
Trance Development
Greetings,
I am having problems compiling Postgres 6.4.2 on Solaris 7.
I know, 6.4?, why aren't you using 7.1/7.2. Well, a number
of our clients still use 6.4. We will upgrade them to 7.1/7.2
later this year.
In the meantime, I have been given another development box
on which I need to
My guess is that you are being bitten by a bug we had with the sed
scripts in those old releases. Seems newer seds are more prone to
trigger that bug. As I remember, it was something about the sed's and
backslashes in one of the *.sh files in the backend directory. I don't
remember more. Try
On 14 Mar 2002 21:17:05 +
Oliver Elphick [EMAIL PROTECTED] wrote:
On Thu, 2002-03-14 at 20:13, Jie Liang wrote:
I did everything as you did, however, when start the postmaster,
I got following:
FATAL 1:'syslog' is not a valid option name.
Then you haven't configured postgresql
Larry Rosenman [EMAIL PROTECTED] writes:
Hackers: Is there any reason to NOT make --enable-syslog the default
any more?
I.E. can we change the sense of it to be --disable-syslog and have
USE_SYSLOG defined by default?
I thought we'd agreed to do that already; at least Peter had indicated
21 matches
Mail list logo
