Re: [ADMIN] pg_log: no such file or directory

Yow, 7.0. You should probably upgrade soon. 7.3 will be released in a few weeks. --- Bhuvan A wrote: > > > I use postgresql 7.2. Last night i received a strange error and the > > > postmaster was crashed. It reported >

Re: [ADMIN] pg_log: no such file or directory

> > I use postgresql 7.2. Last night i received a strange error and the > > postmaster was crashed. It reported > > 'cannot read block 1470 of pg_log: no such file or directory'. > > There is no pg_log in 7.2. You'll need to be more accurate about your > situation if you want help ... > Sorry

Re: [ADMIN] user functions

SELECT * from pg_proc where proname=''; > Hello list: > > Has anybody know how to see all user function, and how to see the code? Not with >pg_access. I > mean command line in psql? > > Thanks in advance. > > ---(end of broadcast)--- TIP 4: >Don'

[ADMIN] user functions

Hello list: Has anybody know how to see all user function, and how to see the code? Not with pg_access. I mean command line in psql? Thanks in advance. ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster

[ADMIN] Some silly questions

I was just wondering about a few options that I would think might be pretty useful. They might exist, but then, I don't know how to get it done... Here's my list: - multi-volume database. Is it possible to split the complete database so it will use several disks? One reason might be load-balancing

Re: [ADMIN] ODBC error

Hi, I updated the table definitions and changed the field type from numeric(18) to int for the field I was linking the tables with. This solved the problem. However, if a decimal field was required, I think this would cause a big problem. Is there a workaround if a decimal field is required?

[ADMIN] ODBC error

Hi, I am trying to create a report using Crystal Reports 8.0. I have downloaded and installed the latest ODBC driver (hoping this would solve the problem). I get the following error: ODBC error: ERROR: Unable to identify an operator '=' for types 'numeric' and 'float8' You will have t

Re: [ADMIN] pg_upgrade problems

I thought we disabled pg_upgrade for 7.2.X because we found we had problems, I think with dealing with the transaction log files. --- Nick Sayer wrote: > I just got done upgrading 2 databases from 7.1.x to 7.2.3. In both cas

Re: [ADMIN] pg_log: no such file or directory

Bhuvan A <[EMAIL PROTECTED]> writes: > I use postgresql 7.2. Last night i received a strange error and the > postmaster was crashed. It reported > 'cannot read block 1470 of pg_log: no such file or directory'. There is no pg_log in 7.2. You'll need to be more accurate about your situation if yo

[ADMIN] pg_upgrade problems

I just got done upgrading 2 databases from 7.1.x to 7.2.3. In both cases the procedure outlined in pg_upgrade.1 failed. In one case, the failure was catastrophic. In neither case was any data lost (because I backed up with pg_dumpall first), but in both cases it appears the failure was similar: