Re: [ADMIN] all postgres users do "not exist"

tually just points to another one which has the real data that psql might have been confused. /usr/local/pgsql/data lrwxrwxrwx 1 root other 22 Apr 18 2006 data -> /home/local/pgsql/data /home/local/pgsql/data drwx-- 10 postgres staff 512

[ADMIN] all postgres users do "not exist"

that the local data directory (/usr/local/pgsql/data) pointsto another data directory at the root of the postgres unix account whichreally contains the database data (/home/local/pgsql/data).  Is thereany way to reinitialize while preserving the existing data directory(dbinit??)?         Thanks,W

[ADMIN] Fwd: Question: 2 GB file limit on linux

Hi, I sent this request recently but have heard nothing. I'm new to he whole procedure and may be doing this incorrectly. Please advise. Thanks Will Lewis Database Administrator (DBA) Central IT Romney House Bristol City Council (0117 9222736) --- Begin Message --- I saw a reference some

Re: [ADMIN] No space left on device

space left on device Umm well my first guess is that you are out of drive space. I assume you checked that already? Will ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings

Re: [ADMIN] pg_hba.conf

pgsql configration file , please stop the postgresql and then make changes and restart it again. This is uncessary for pg_hba.conf edits. Simply call pg_ctl reload to reread the access list. Will ---(end of broadcast)--- TIP 6: Have you searched

Re: [ADMIN] corrupt data - caused by lm-sensors?

ave suggested in that you have some bad hardware on that machine. Note that this shouldn't have caused the drive corruption unless the segfault took out a piece of the disk io kernel subsystem. Although I have to say that using development versions of software on production machines is not necessarily the most safe practice one can engage in. Sincerely, Will LaShell > > Thanks for feedback. > > Zeno signature.asc Description: This is a digitally signed message part

Re: [ADMIN] 7.2.3 -> 7.3.2: timeofday(), server crashed

> > ERROR: parser: parse error at or near "602869" at character 1 > > LOG: server process (pid 31373) was terminated by signal 9 > > This is also unrelated. There is no scenario in which a parse error > will lead to signal 9. I would guess that you have on

Re: [ADMIN] index not used in ( varchar = text )

Why would you want to cast that to text, if your field is a varchar? I wouldn't think you would have to cast it at all, or if you do, cast it to a varchar. Curious, WIll On Sat, 2003-02-22 at 10:55, Gaetano Mendola wrote: > Hi all, > > why in Postgresql 7.3.2 in a select lik

Re: [ADMIN] Replication

On Tue, 2003-01-28 at 11:01, Marc G. Fournier wrote: > On Tue, 28 Jan 2003, Will LaShell wrote: > > > Hrmm, this is kind of sad. rserv actually does work pretty well. We use > > it in a production environment here at OFS on a medium size database > > cluster. > > I

Re: [ADMIN] Replication

On Tue, 2003-01-28 at 14:12, Andrew Sullivan wrote: > On Tue, Jan 28, 2003 at 09:59:52AM -0700, Will LaShell wrote: > > What problems have people been having getting rserv to work at all? > > In 2001 I tested it for our anticipated load. It worked for me, but > it was not up t

Re: [ADMIN] Replication

e replication option, but it doesn't work at all, and has even worse documentation. > cheers > > Fabian > Will signature.asc Description: This is a digitally signed message part

Re: [ADMIN] Replication

ers in theory releasing updates to rserv every year or so? ( At least that's what has been said in the past. ) What problems have people been having getting rserv to work at all? Will LaShell signature.asc Description: This is a digitally signed message part

Re: [ADMIN] offsite warm backup suggestions?

well for us, and it introduces another program that could cause the system to fail. > > Yes. We use the rserv (eRServer) software from PostgreSQL, Inc. It > works for us. We use rserv here at work as well. > You can't use rsync for this. It will destroy data. > > The

[ADMIN] Interesting date/time 60 second problem with Postgresql

s something that was fixed? Sincerely, Will LaShell signature.asc Description: This is a digitally signed message part

Re: [ADMIN] Using oid with RServ w/ Postgresql 7.2

On Thu, 2002-10-17 at 18:55, Tom Lane wrote: > Will LaShell <[EMAIL PROTECTED]> writes: > > My question would then be, are there any problems/reasons or hints with > > using the oid field as the field that the rserv trigger is set on? > > We will be using rserv in a pr

Re: [ADMIN] Using oid with RServ w/ Postgresql 7.2

On Thu, 2002-10-17 at 18:55, Tom Lane wrote: > Will LaShell <[EMAIL PROTECTED]> writes: > > My question would then be, are there any problems/reasons or hints with > > using the oid field as the field that the rserv trigger is set on? > > We will be using rserv in a pr

[ADMIN] Using oid with RServ w/ Postgresql 7.2

d, and it seems to work. My question would then be, are there any problems/reasons or hints with using the oid field as the field that the rserv trigger is set on? We will be using rserv in a production environment so I'm looking at this as not just an academic solution but a real world one

[ADMIN] developer deleted a database directory, postgres won't start

done anything this stupid so I have no idea where to look? Thank you so much for the help Sincerely, Will LaShell -- --- "Doh.. STUPID STUPID STUPID" --an excerpt taken from every developers cvs commit message at some point ---