Hi,
I have isolated the corrupted row of data and isolated column which
constains bad data. Unfortunately I can't do anything with the row. I have
an older backup of the db which contains correct row. Is there a way I can
restore only the given row or replace it in the file ( I also located the
ro
> -Original Message-
> From: pgsql-admin-ow...@postgresql.org [mailto:pgsql-admin-
> ow...@postgresql.org] On Behalf Of Kasia Tuszynska
> Sent: Tuesday, November 29, 2011 3:35 PM
> To: Kevin Grittner; pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] transaction error handling
>
> Hi Kevin
Hi,
Yes, I believe that you are right.
As far as I can gather, the postgres transaction error handling is like oracle
stored procedures. If you do not catch the error the whole transaction is
rolled back. I am curious why Postgres has gone with a model that does not
allow the user a choice to d
On Tue, 29 Nov 2011 09:57:24 -0800, Kasia Tuszynska wrote:
> Hi Everybody,
>
> This is an architectural question.
> I am testing on Postgres 9.0.2 on windows and linux(suse, rhel, ubuntu)
>
> I want to make sure that I have the correct understanding of the
> Postgres architecture and would like
On 11/29/2011 01:06 PM, Colin E Busse wrote:
Hello,
I am trying to determine how to get postgres to use a custom
postgresql.conf file that will be located in a directory other than
the default postgresql.conf file. I would like it to be installed via
an rc script so that the database setup c
Hello,
I am trying to determine how to get postgres to use a custom
postgresql.conf file that will be located in a directory other than the
default postgresql.conf file. I would like it to be installed via an rc
script so that the database setup can be part of a self-contained install.
I do
On Tue, Nov 29, 2011 at 10:57 AM, Kasia Tuszynska wrote:
> Postgres:
> Begin transaction
> Insert - no error
> Insert - error raised
> Transaction loss = no implicit rollback to the single error free insert.
>
> Is this a correct interpretation of the Postgres transaction error handling?
> If so,
Hi Kevin,
Thank you, that is very helpful.
I am not worried about the implicit commits. The "no implicit savepoint" was
more of an issue, since it created a necessity to create and destroy savepoints
per each sql statement to capture any statement level error without losing a
transaction, that a
Kasia Tuszynska wrote:
> Oracle:
> Begin transaction
> Insert - no error
> Implicit savepoint
> Insert - error raised
> Implicit rollback to the savepoint, no transaction loss, error
> raised on the insert statement that errored out.
> End transaction, implicit commit, with the single error free
On Tue, Nov 29, 2011 at 11:15 AM, Craig James
wrote:
> Several times recently one of our databases has gotten stuck with the
> following situation:
>
> postgres=# select datname, procpid, usename, current_query from
> pg_stat_activity where current_query != '';
> datname | procpid | usename |
Several times recently one of our databases has gotten stuck with the
following situation:
postgres=# select datname, procpid, usename, current_query from
pg_stat_activity where current_query != '';
datname | procpid | usename |
current_query
+-+--+
Hi Everybody,
This is an architectural question.
I am testing on Postgres 9.0.2 on windows and linux(suse, rhel, ubuntu)
I want to make sure that I have the correct understanding of the Postgres
architecture and would like to enquire if there are any plans to change it.
Comparing Oracle and P
On Mon, Nov 28, 2011 at 9:48 PM, Craig Ringer wrote:
>
> Getting a usable stack trace on Windows isn't actually too hard.
The problem isn't getting the trace - I know how to do that - it's that I
don't have the pdbs for this build, and so the trace wouldn't be very
useful. I may be able to get
13 matches
Mail list logo
