Rajesh Kumar Mallah wrote:
>
> Hi,
>
> Is it possible to log the statements and durations of executed
> queries into a special table for later analysis. Or capturing the
No table option.
> logfile and parsing it the only way? In the case of latter is it
> possible to use syslog to pipe the line
"Chris White (cjwhite)" <[EMAIL PROTECTED]> writes:
> My 7.2.1 database was in the middle of inserting a large object when the
> power went down.
You really, really, really should be on 7.2.4 (if not 7.3.*). We don't
make dot-releases for amusement's sake --- there are some critical bug
fixes bet
Title: Message
My 7.2.1 database was in the middle of inserting a large
object when the power went down. When I restart the database I getting the
following messages:
postgres:
startup subprocess : DEBUG sql sql sql DEBUG:
database system was interrupted at
2003-10-08 09:29:12 PDTpostg
Pedro Miguel Guedes <[EMAIL PROTECTED]> writes:
> On the old system I did the query:
> SELECT * FROM contactos WHERE empresa_nome ILIKE ´%nestlé%´;
> and it did work
> O the new system it does not produce nothing!???
I think you have the wrong locale setting in your new database. The
database loc
Jeff Boes <[EMAIL PROTECTED]> writes:
> [How would a plperl function that changes the local behavior of SIGALRM
> affect the backend?]
IIRC, SIGALRM is used for two things: one, to trigger a deadlock check
cycle if we wait too long for a lock (see deadlock_timeout), and two,
to implement statemen
Hi,
Is it possible to log the statements and durations of executed
queries into a special table for later analysis. Or capturing the
logfile and parsing it the only way? In the case of latter is it
possible to use syslog to pipe the lines through a program
can anyone please share the config if he
On Wed, Oct 29, 2003 at 02:08:03PM -0500, Andrew Biagioni wrote:
>
> So finally, my question. Why is this behavior present? Is it actually
> a feature that I don't know enough to appreciate?
It's the side-effect of some other features in the system. If you
search on -hackers archives you'll
I have a crazy problem here.
Nobody seems to known why.
I am not a database expert nor do known much about
Postgres.
I am just a system administrator trying to move a database from
one system to another.
O the old system (slackware linux) the postgres was downloaded
an compiled from source.
O the n
Title: PostgreSQL Metadata
Great,
thank you both for your replies.
Best regards,
David B. Wagoner Database Administrator Arsenal Digital
Solutions Web: http://www.arsenaldigital.com
"the most trusted
source for STORAGE
MANAGEMENT SERVICES"
The contents of this e-mail message
Yes PostgreSQL does support COMMENTing on wide
range of objects in the same manner as Oracle.
rt3=# \h comment
Command: COMMENT
Description: define or change the comment of an object
Syntax:
COMMENT ON
[
TABLE object_name |
COLUMN table_name.column_name |
AGGREGATE agg_name (agg_t
On Thu, 30 Oct 2003, David Wagoner wrote:
> In Oracle, you can "select * from dictionary" to see the data dictionary
> table names and descriptions. Is there something similar in PostgreSQL?
Old way (still supported, not going away):
\d from a psql session
New way: select * from information_s
Title: PostgreSQL Metadata
In Oracle, you can "select * from dictionary" to see the data dictionary table names and descriptions. Is there something similar in PostgreSQL?
Also, in Oracle you can store comments on tables and columns which provides valuable metadata. Is this also possible in
Tom Lane wrote:
[ thinks... ] Another possibility is that you are running some
non-Postgres code that resets SIGALRM handling to default. I have
heard rumors that Perl will do that in some cases, for example.
Are you using plperl?
Yes, we are. I know there are some places in the code where SI
Jeff Boes <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> What's signal 14 on your machine? (Look in /usr/include/signal.h to
>> be sure.) Also, what PG version is this?
> 14) SIGALRM
> This is Pg 7.3.4, running on Linux 7.3 (Kernel 2.4.18-18.7.xsmp on a
> 2-processor i686).
Hm. That do
Jeff Boes <[EMAIL PROTECTED]> writes:
> We are experiencing the following error, usually during our nightly
> delete-and-vacuum cycle (when there are very few other connections to
> the database):
> 2003-10-30 01:36:59 [25392] LOG: server process (pid 697) was
> terminated by signal 14
What'
Tom Lane wrote:
Jeff Boes <[EMAIL PROTECTED]> writes:
We are experiencing the following error, usually during our nightly
delete-and-vacuum cycle (when there are very few other connections to
the database):
2003-10-30 01:36:59 [25392] LOG: server process (pid 697) was
terminated by
Hello all!
Postgres says that it is in recovery mode.
The log tells me:
-
Oct 30 02:21:32 daisy postgres[1122213]: [197] NOTICE:
RegisterSharedInvalid: SI buffer overflow
Oct 30 02:21:32 daisy postgres[1122213]: [197] NOTICE:
RegisterSharedInvalid: SI buffer overflow
Oct 30 02:2
We are experiencing the following error, usually during our nightly
delete-and-vacuum cycle (when there are very few other connections to
the database):
2003-10-30 01:36:59 [25392] LOG: server process (pid 697) was
terminated by signal 14
2003-10-30 01:36:59 [25392] LOG: terminating any oth
Hi!
Try with this:
-Mensaje original-
De: Anna Kanevsky [SMTP:[EMAIL PROTECTED]
Enviado el: Jueves 2 de Octubre de 2003 20:45
Para: 'Stephan Szabo'
CC: '[EMAIL PROTECTED]'
Asunto: Re: [ADMIN] Delete accident
Thank you everyone!
I got a load of responses, and don't want to
hello
I accidentally deleted every recordes from my table
whithout a back up for my data such as pg_dump.
How can I restore
them?
I found that deleted data are alrealy in my databes
files such as /var/lib/pgsql/data/base/*
and transactions are loged in
/var/lib/pgsql/data/pg_xlog/0001,2
Dear All,
I have updated the release of my Postgres Database, from 7.0 to 7.3.
From the old version, I effected the following query to retrieve type and
length of a specific table field:
select *from pgadmin_tables where (table_name='".$strTableName."') AND
(column_name='".$strColumName."')
Ho
21 matches
Mail list logo
