> We are running into a situation where psql is aborting the transaction
> when one call returns an error. Is there a way to continue on with
> transaction or at least save what has already happened (like an Oracle
> Save Point)?
Not yet, although savepoints have been talked about. (maybe 7.3?
One more thing...
The vacuum command is giving the same error:
[root@s1 data]# vacuumdb -v -U postgres dans_pgsql
Password:
Asql: FATAL 1: cannot find attribute 24 of relation
vacuumdb: vacuum dans_pgsql failed
Is there another way to fix a corrupt database (assuming that is what the
problem
Help!
One of my customers is having a problem with their database causing all of
their sites to be down right now. The problem seems to effect only their
database, not any other databases on the server. Here is the output when
connecting to it:
[root@s1 data]# psql -U postgres dans_pgsql
Passw
Hi, I searched the mailing list and I am stuck.
INFO :
> monitorar=# SHOW DateStyle ;
> NOTICE: DateStyle is SQL with European conventions
> SHOW VARIABLE
>
> monitorar=# SELECT oid from reservas where data_comp = '20/08/2001';
> oid
>
> 254376
> (1 row)
>
> monitorar=# \d reservas
Hi, I searched the mailing list and I am stuck.
INFO :
> monitorar=# SHOW DateStyle ;
> NOTICE: DateStyle is SQL with European conventions
> SHOW VARIABLE
>
> monitorar=# SELECT oid from reservas where data_comp = '20/08/2001';
> oid
>
> 254376
> (1 row)
>
> monitorar=# \d reserva
On Mon, 10 Sep 2001 01:25:59 + (UTC), Tim Boring <[EMAIL PROTECTED]>:
> Can you change a column modifier after you've created the table? For
> example, I have a table called "authors" with the following columns:
> authorid, authorfirstname, authorlastname, authormi, statecode, country,
> born
But can I do that?
e.g.
There is a customers table that keeps customers record but for two
company: A & B.
can I store A's customers & B's customers record into two different
directory? That is the mean I know for table partitioning. Is that right?
thx,
Corn
> In 7.1.3 and 7.2, there are only 2-3 WAL files kept because
> there is no need to keep them after a checkpoint. Is there
> any need to have these WAL config paramaters anymore?
I missed what's you propose to remove.
Vadim
---(end of broadcast)--
Hi all-
I caused a crash by filling up the filesystem that pg_xlog lives on whilst
doing a vacuum analyze. When I looked at the remains, there were 3 WAL files
out there & no space left.
I tried simply restarting (/etc/init.d/postgresql start) in the hopes that
the mess would get cleaned, but wi
Hi,
I'm just trying to install version 7.1.3 on an AIX 4.3.3 system from
source. After unpacking the archive I ran:
./configure --with-tcl --without-tk --enable-odbc --enable-syslog
This works fine without error.
After this I ran "make" without any option.
This results in the following error mess
> 4) I cant connect using ODBC in ER/WIN any more.
> I get : password crypt authetification not supported.
>
> 5) I cant connect using ODBC in pgAdmin any more.
> I get : Incorrect password
Think I found it : ODBC doesn't seems to support crypt.
---(end of broa
> > > In 7.1.3 and 7.2, there are only 2-3 WAL files kept because
> > > there is no need to keep them after a checkpoint. Is there
> > > any need to have these WAL config paramaters anymore?
> >
> > I missed what's you propose to remove.
>
> I am not proposing to remove anything. I just want to
We are running into a situation where psql is
aborting the transaction when one call returns an error. Is there a way to
continue on with transaction or at least save what has already happened (like an
Oracle Save Point)?
13 matches
Mail list logo
