Обсуждение: create procedure

Catch all the cricket action. Download Yahoo! Score tracker

On Thu, Apr 24, 2003 at 07:05:28 +0100,
  sivasankaran <shankar_cva@yahoo.co.in> wrote:
> Hello sir,
>
> I don't see the create procedure command in PostgreSQL. Do you
> tell me how to do it? or which document do I have to read?

Create function is the postgresql equivalent.
Take a look at:
http://www.postgresql.org/docs/view.php?version=7.3&idoc=0&file=xfunc.html

Hi,

We just had a problem on the hard disk we resolved with fsck.

Database server runs, queries on the DB seems ok, but when we do a
vacuum (full or not), we have after some tables were vaccumed :

mai  2 11:49:34 aphrodite logger: PANIC:  XLogFlush: request
635F6373/6B636568 is not satisfied --- flushed only to 14/F9473CF4
mai  2 11:49:34 aphrodite logger: LOG:  statement: SET autocommit
TO 'on';VACUUM  VERBOSE ANALYZE
mai  2 11:49:34 aphrodite logger: LOG:  server process (pid 3673)
was terminated by signal 6
mai  2 11:49:34 aphrodite logger: LOG:  terminating any other active
server processes
mai  2 11:49:34 aphrodite logger: LOG:  all server processes
terminated; reinitializing shared memory and semaphores
mai  2 11:49:34 aphrodite logger: LOG:  database system was
interrupted at 2003-05-02 11:49:31 CEST
mai  2 11:49:34 aphrodite logger: LOG:  checkpoint record is at
14/F89F89A0
mai  2 11:49:34 aphrodite logger: LOG:  redo record is at
14/F89F89A0; undo record is at 0/0; shutdown TRUE
mai  2 11:49:34 aphrodite logger: LOG:  next transaction id:
121015461; next oid: 9816181
mai  2 11:49:34 aphrodite logger: LOG:  database system was not
properly shut down; automatic recovery in progress
mai  2 11:49:34 aphrodite logger: LOG:  redo starts at 14/F89F89E0

and the vacuum stops...

Is there a solution or can I just do a pg_dump of the DB, the re-init the
DB and resotring the db ?

thank you




On 24 Apr 2003 at 7:05, sivasankaran wrote:

>
> Hello sir,
>
> I don't see the create procedure command in PostgreSQL. Do you
> tell me how to do it? or which document do I have to read?
> Catch all the cricket action. Download Yahoo! Score tracker


Jean-Arthur Silve
EuroVox
4, Place Félix Eboué
75583 Paris Cedex 12
T : +33 1 44670505
F : +33 1 44670519

JEANARTHUR@EUROVOX.FR writes:
> We just had a problem on the hard disk we resolved with fsck.

> Database server runs, queries on the DB seems ok, but when we do a
> vacuum (full or not), we have after some tables were vaccumed :

> mai  2 11:49:34 aphrodite logger: PANIC:  XLogFlush: request
> 635F6373/6B636568 is not satisfied --- flushed only to 14/F9473CF4

Hm... I can't see how vacuum could get to that state --- XLogFlush
failure within vacuum should only be an ERROR not PANIC.  I wonder
whether that was actually coming from a background checkpoint process?
(checkpoint shouldn't be PANICing either, but it looks like it would
at the moment :-()

But I digress.  Your problem is evidently that you've got clobbered
table data.  XLogFlush is unhappy because the first eight bytes of some
page have been overwritten with junk (text, it looks like: in ASCII that
value works out as "sc_check" ...).  Whatever that page is, it's toast
now, but your problem is to identify it --- if you're really lucky it's
in an index or some other noncritical file.

You might try writing a little script in perl or some such to grovel
through all the database files looking for 8K pages that don't start
with small integers --- 00000000 to 00000014 are evidently the only
valid values.  There could be more than one trashed page, but hopefully
there aren't many.  Once you know the filenames containing the trashed
pages, see contrib/oid2name to identify what tables they are, and then
report back and we can give you advice about how to recover.  You'll
probably end up zeroing out the trashed pages, but the first problem
is to know where they are.

            regards, tom lane