Update - someone unleashed a 'cleanup script' yesterday via puppet to
multiple hosts and greedily deleted files that had not been modified in 15
days. This is the most likely culprit so mystery basically solved.
Thankfully this is in QA, whew! It would be interesting to still know if
there are w
Alejandro Brust escribió:
> U could try some like "SET/ zero_damaged_pages = on"and perform a
> vacuum-db and may be pg_dump
I don't think this is a good idea. It might cause data loss. In any
case it's unlikely to fix the reported problem.
--
Álvaro Herrerahttp://www.2nd
El 04/10/2013 14:10, Mike Broers escribió:
> Strange, this is happening in a totally different environment now too.
> The only thing these two environments share is a SAN, but I wouldnt
> think something going on at the SAN level would make files disappear.
> Any suggestions are greatly apprecia
Strange, this is happening in a totally different environment now too. The
only thing these two environments share is a SAN, but I wouldnt think
something going on at the SAN level would make files disappear. Any
suggestions are greatly appreciated.
On Fri, Oct 4, 2013 at 9:40 AM, Mike Broers
El 04/10/2013 11:40, Mike Broers escribió:
> Hello, our postgresql 9.2.4 qa database (thankfully its just qa) seems
> to be hosed.
>
> Starting at around 3:39am last night I started seeing errors about
> missing files and now I cannot run a pgdump or a vacuum without it
> complaining about files
amjad usman wrote:
> ERROR: index row size 3176 exceeds maximum 2712 for
> index "description_department_of_aeronautics_and_astronautics_5_pkey"
Can you show us the definitions of the table and the index?
-Kevin
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make change
On 23 October 2012 10:15, Craig Ringer wrote:
>
> First, try per-database dumps. Work out which database has the problem.
> Do a:
>
> pg_dumpall -U sns84 --globals-only > globals.sql
>
> then for each database:
>
> pg_dump -U sns84 -f $dbname.sql $dbname
>
> (scripting it if desired),
On 10/22/2012 03:24 AM, Terry Khatri wrote:
> Hi
>
> I am getting the following error msg when I do a pg_dumpall
>
> -
>
> TK@OraLinux /usr/local/pgsql/backups
> $ pg_dumpall -U sns84 > completebackup20121020,sql
> pg_dump: schema with OID 74363 does not exist
> pg_dumpall: pg_dump failed on
SOLVED.
So it turns out that you can't access unlogged tables on the replica:
exchange_prod=# select count(1) from office_imports;
ERROR: cannot access temporary or unlogged relations during recovery
The solution was to add the --no-unlogged-table-data option to pg_dump and it
btw, I just realized... this table that it's failing on is unlogged. I'm
beginning to do some googling based around that tidbit of information, but I
wanted to get that clarification on here sooner rather than later.
Thanks!
...spike
On Sep 27, 2012, at 1:29 PM, Spike Grobstein wrote:
> Hi,
On 7/19/2012 10:33 PM, Madhu.Lanka wrote:
Hi Friends
I am creating the function like
CREATE OR REPLACE FUNCTION getrowstest3(pname character varying,ppassword
character varying)
RETURNS SETOF getrows AS
$BODY$
declare
r getrows;
begin
for r in EXECUTE
'select
u.role_id,u.user_id,p
.orgDate:20/07/2012 08:29Subject: Re: [ADMIN] ERROR: there is no parameter $1Sent by:pgsql-admin-ow...@postgresql.orgOn Fri, Jul 20, 2012 at 6:33 AM, Madhu.Lanka wrote:> I am getting the following error>> ERROR: there is no parameter $1> LINE 5: r.role_id = u.role_i
Hi pgsql-admin-ow...@postgresql.org wrote on 20/07/2012 03:33:36:> From: "Madhu.Lanka" > To: , > Date: 20/07/2012 06:37> Subject: [ADMIN] ERROR: there is no parameter $1> Sent by: pgsql-admin-ow...@postgresql.org> > Hi Friends> > I am creating the function like > > CREATE OR REPLACE FUNCTION get
On Fri, Jul 20, 2012 at 6:33 AM, Madhu.Lanka wrote:
> I am getting the following error
>
> ERROR: there is no parameter $1
> LINE 5: r.role_id = u.role_id and p.name= $1 and p.password = $2
Because they are not expanding inside strings. Use EXECUTE ... USING ...
EXECUTE '... and p.name =$1 and
On 07/09/2012 09:26 PM, Eduardo Sá dos Reis wrote:
Hi,
In my Postgres log the message is occurring:
1 4ffad9f4.67db 2012-07-09 10:17:40 BRT LOG: connection received:
host=10.20.0.1 port=2368
2 4ffad9f4.67db 2012-07-09 10:17:40 BRT LOG: connection authorized:
user=usu_cad database=prd_cad
3 4ffa
Kshirsagar, Swanand wrote:
> I am using Postgres version 8.3.17 on one of my database server. I
have received a .sql dump file from
> my client. Which is supposed to be taken from a Postgres 8.3.7 db.
Now, I have created an empty
> database and I am trying to restore the .sql file with command psql
Karuna Karpe wrote:
> 2011-12-23 11:44:18 ISTLOG: restored log file
> "0001000F" from archive
> 2011-12-23 11:44:18 ISTLOG: record with incorrect prev-link
> 0/E94 at 0/F20
> 2011-12-23 11:44:18 ISTLOG: redo done at 0/EC0
> 2011-12-23 11:44:18 ISTLOG: restored log
I have issue during PITR. this log as follow:
2011-12-23 11:44:18 ISTLOG: database system was shut down at 2011-12-23
11:41:37 IST
2011-12-23 11:44:18 ISTLOG: starting archive recovery
2011-12-23 11:44:18 ISTLOG: restored log file "0001000F"
from archive
2011-12-23 11:44:18 ISTL
you are right. my bad :)
On Thu, Dec 22, 2011 at 3:32 PM, Jerry Sievers wrote:
> MirrorX writes:
>
> > is it possible that the timestamp that you put there ('2011-12-22
> 07:27:08') is before the time that you issued the
> > command pg_stop_backup? you can check that by looking at the
> backup.l
MirrorX writes:
> is it possible that the timestamp that you put there ('2011-12-22 07:27:08')
> is before the time that you issued the
> command pg_stop_backup? you can check that by looking at the backup.label
> file where is says when the backup was
> finished.
It is the *backup file that g
is it possible that the timestamp that you put there ('2011-12-22
07:27:08') is before the time that you issued the command pg_stop_backup?
you can check that by looking at the backup.label file where is says when
the backup was finished.
you can only use point in time recovery after the point whe
Thanks to all for giving solution.
On Fri, Nov 11, 2011 at 8:24 AM, Craig Ringer wrote:
> On 11/10/2011 02:29 PM, Karuna Karpe wrote:
>
> 1) what is tablespace in postgres?
>>
>
> It's a way of putting some tables, indexes, etc into a different part of
> your system's storage. Sometimes yo
On 11/10/2011 02:29 PM, Karuna Karpe wrote:
1) what is tablespace in postgres?
It's a way of putting some tables, indexes, etc into a different part of
your system's storage. Sometimes you want to do this to put a really big
table on slower, cheaper storage. Sometimes you might want to
On Nov 10, 2011, at 7:01 AM, Karuna Karpe wrote:
> what's wrong in above. why not able to connect to database??
Your disk is full?
--
Scott Ribe
scott_r...@elevated-dev.com
http://www.elevated-dev.com/
(303) 722-0567 voice
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
Karuna Karpe wrote:
> 2011-11-10 18:46:40 ISTPANIC: could not write to file
> "pg_xlog/xlogtemp.8737": No space left on device
> 2011-11-10 18:46:40 ISTLOG: startup process (PID 8737) was
> terminated by signal 6: Aborted
What does df show if you run it at that point?
-Kevin
--
Sent via
On Thu, Nov 10, 2011 at 12:36 AM, Uwe Schroeder wrote:
>
>
>> Hello,
>>
>> 1) what is tablespace in postgres?
>>
>> 2) one more issue is that, I try to rename or delete some file in
>> /opt/PostgresPlus/9.0/data/base/16428/ directory. when I restart postgres
>> server, it start normally
> Hello,
>
> 1) what is tablespace in postgres?
>
> 2) one more issue is that, I try to rename or delete some file in
> /opt/PostgresPlus/9.0/data/base/16428/ directory. when I restart postgres
> server, it start normally. but I thing this is wrong. I rename or delete
> file into a
On 29/10/11 19:07, Jelena Gorelikova wrote:
>
> During the istall of a new version of PostgreSQL 9.1 on Windows 7
> (64bit) machine I`got the following error:
>
> A fatal error occur whilst loading database modules. Problem running
> post-install step. Installation may not complete correctly.
>
Lukasz Brodziak wrote:
> I have a problem with conncting to db. Whe I try to connect I get
> either: ERROR: type "pg_catalog.int4" does not exist or Cache
> lookup failed for type 23. Is there a way of recreating the type
> because I heve to get to the data from this particular db as the
> dump
Thanks Tom.
I executed a REINDEX DATABASE and received the error:
.
.
.
NOTICE: table "pg_enum" was reindexed
NOTICE: table "pg_namespace" was reindexed
NOTICE: table "pg_conversion" was reindexed
NOTICE: table "pg_depend" was reindexed
NOTICE: table "users" was reindexed
NOTICE: table "resu
=?ISO-8859-1?Q?Diego_Fern=E1ndez_Slezak?= writes:
> Hello everybody,
> I had a hard drive failure last week. After lots of effort I've been able to
> backup a 700GB database, with only one file with corruption.
> When I do some big queries, it throws me errors on this faulty file:
> could not rea
Saurabh Agrawal, 20.04.2011 08:38:
Hi All,
I am trying to alter column from "timestamp without timezone" to
"bigint" but getting below error:
#ALTER TABLE test ALTER column time type bigint;
#ERROR: column "time" cannot be cast to type bigint
Is there any other method for alter column to bigi
On Thu, Mar 24, 2011 at 1:43 PM, raghu ram wrote:
>
>
> On Thu, Mar 24, 2011 at 6:09 PM, Stevie wrote:
>>
>> Hello pgsql-admins,
>>
>> we have a problem with our Postgresql 9.0.3 backup database (Ubuntu 10.4).
>> The backup and restore is done as described here:
>> http://www.postgresql.org/docs/
Hello
> There is a commit log corruption in your database.
Yes, and it seems this is produce by a pg_upgrade bug from pg8 to pg9 in
October 2010.
> You need to make the files with right size (256K of zeroes).A suitable
> "dd" from /dev/zero will accomplish this on modernUnixen (ie, anything
> t
On Thu, Mar 24, 2011 at 6:09 PM, Stevie wrote:
> Hello pgsql-admins,
>
> we have a problem with our Postgresql 9.0.3 backup database (Ubuntu 10.4).
> The backup and restore is done as described here:
> http://www.postgresql.org/docs/9.0/static/continuous-archiving.html
> If you want to know the
On Tue, Mar 1, 2011 at 2:39 AM, Arnold, Sandra wrote:
> I am running the following initdb command and get the following error.
>
> initdb -A md5 -D /pgsql/ftrp/data9 -E UTF8 --locale=C -U postgres -W
> initdb: error while loading shared libraries:
> /app/PostgreSQL/9.0/lib/libedit.so: cannot res
Hi All,
Thank you for your reply.
Let me explain a bit more in detail.
This is the first time I am installing PostgreSQL Advanced Server. I do not
have any database yet, except for the edb database.
OS : Fedora 14
PostgreSQL Version : PPAS 8.4.7
I downloaded from enterprisedb website.
Installati
Maalini -
On first glance (and not knowing the architecture of your particular
'service'), this looks very explainable on the basis of PostgreSQL being
instructed to do a 'graceful' shutdown - while you may have users connected.
Depending on how your service 'stop' issues the shutdown comma
On Thu, 2011-02-24 at 10:20 +0800, Maalini Samuganardan wrote:
> [root@edbws01 run]# service postgresql start
> Starting postgresql service: [ OK ]
> [root@edbws01 run]# service postgresql stop
> Stopping postgresql service: [FAILED]
Co
Maalini Samuganardan wrote:
> I am getting an error when try to stop the postgresql server.
> No problem starting.
>
> Please find error message below.
>
> Thank you.
>
> [root@edbws01 run]# service postgresql status
> postmaster is stopped
> [root@edbws01 run]# service postgresql start
> Sta
Victor Hugo dos Santos writes:
> On Tue, Jan 4, 2011 at 1:05 PM, Tom Lane wrote:
>> It looks like a corrupted-data problem from here. You need to isolate
>> and delete the bad row(s).
> # su - postgres -c "psql bacula -c 'SELECT md5 from public.file OFFSET
> 1417610 LIMIT 1'"
> server closed th
On Tue, Jan 4, 2011 at 1:05 PM, Tom Lane wrote:
> Victor Hugo dos Santos writes:
>> any idea ???
>
> It looks like a corrupted-data problem from here. You need to isolate
> and delete the bad row(s).
Hello again...
this is very, very strange !! :D
(sorry for long message, but I'm trying to sen
On Tue, Jan 4, 2011 at 1:05 PM, Tom Lane wrote:
> Victor Hugo dos Santos writes:
>> any idea ???
>
> It looks like a corrupted-data problem from here. You need to isolate
> and delete the bad row(s).
hello
any sugestion about how found and delete the bad row(s) ??
thanks
--
--
Victor Hugo
Victor Hugo dos Santos writes:
> any idea ???
It looks like a corrupted-data problem from here. You need to isolate
and delete the bad row(s).
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http
On Tue, Jan 4, 2011 at 12:02 PM, Victor Hugo dos Santos
wrote:
[...]
> but, I'm dowloading the 64bit image now and after I install it in a
> Virtual Machine to try.
I'm a stupid !! :(
I can't restore the same DB from 32bit in 64bits !!!
for this, should be export first in 32bits (pg_dump) and a
On Tue, Jan 4, 2011 at 11:07 AM, Thomas Markus wrote:
> hi,
>
> looks like a 32bit version so 4294967293 is too much (4GB). Use a 64bit
> version
.. is a small table (look the size of last dump)
=
$ ls -lh /tmp/public-files.sql
-rw-r- 1 root root 298M Jan 4 11:59 /tmp/public
hi,
looks like a 32bit version so 4294967293 is too much (4GB). Use a 64bit
version
regards
Thomas
Am 04.01.2011 14:48, schrieb Victor Hugo dos Santos:
Hello,
Actually I use postgresql version 8.4.6-0ubuntu10.04 in bacula server
to save information about backups from bacula.
But, 2 days a
Run ulimit -a and verify the max memory size allowed for the postgres
account.(I assume you are running postmaster under the postgres account,
right?) The allowed size should be large enough for the postmaster plus shared
buffers and several other GUCs that require memory.
Bob Lunney
--- O
Run ulimit -a and verify the max memory size allowed for the postgres
account.(I assume you are running postmaster under the postgres account,
right?) The allowed size should be large enough for the postmaster plus shared
buffers and several other GUCs that require memory.
Bob Lunney
--- O
Run ulimit -a and verify the max memory size allowed for the postgres
account.(I assume you are running postmaster under the postgres account,
right?) The allowed size should be large enough for the postmaster plus shared
buffers and several other GUCs that require memory.
Bob Lunney
--- O
On Tue, Jan 4, 2011 at 10:59 AM, Bob Lunney wrote:
> Run ulimit -a and verify the max memory size allowed for the postgres
> account.(I assume you are running postmaster under the postgres account,
> right?) The allowed size should be large enough for the postmaster plus
> shared buffers and s
bakkiya raj wrote:
> We are facing a problem with postgresql partition tables. We are
> querying 2 days old partition table and at the same time we are
> dropping 2 months old partition.Sometimes our queries are getting
> failed with "ERROR: could not open relation with OID 1761740". We
> have s
Great! I made the base backup again as you said, and its working now.
Thanks.
On Mon, Aug 23, 2010 at 12:17 PM, Tom Lane wrote:
> fazool mein writes:
> > I'm trying to test streaming replication. I set up a primary and
> secondary.
> > The primary starts normal, but when I start the standby, i
fazool mein writes:
> I'm trying to test streaming replication. I set up a primary and secondary.
> The primary starts normal, but when I start the standby, it doesn't start
> up. The log looks like this:
> LOG: database system was interrupted while in recovery at log time
> 2010-08-23 13:30:43
Kevin Kempter wrote:
> # select * from comments;
> ERROR: missing chunk number 0 for toast value 1274882 in
> pg_toast_49234
>
>
> I tried this:
>
> # reindex table pg_toast.pg_toast_49234;
> REINDEX
>
>
> but the error still persists.
>
> Thoughts?
Your database is corrupted. Any idea
Siddharth Shah writes:
> PID PPID USER STAT VSZ %MEM %CPU COMMAND
> 13419 13418 nobody R39172 8% 99% postgres --single -P -D
> /var/db -p 5433 xdb
> It's been running from 10 minutes still there is no output or logs.
What does "strace" show that process is doing?
Kevin Grittner wrote:
Siddharth Shah wrote:
xdb=# reindex index pg_class_relname_nsp_index;
Now INDEXing taking High CPU and postgres baffled.
consider doing your recovery in single-user mode
postgres --single -P -D $DATADIR -p 5433 xdb
Same behavior in
Siddharth Shah wrote:
>>> xdb=# reindex index pg_class_relname_nsp_index;
>>>
>>> Now INDEXing taking High CPU and postgres baffled.
>> consider doing your recovery in single-user mode
> postgres --single -P -D $DATADIR -p 5433 xdb
> Same behavior in single mode.
How long did you l
One more point, This is observed two times while product firmware
updates which updates Postgres 8.4.3 from 8.4.1
Abruptly shutdown never leads to this type of corruption while fsync is
always off
Thanks,
Siddharth
Siddharth Shah wrote:
Kevin Grittner wrote:
[rearranged to put the most cr
Kevin Grittner wrote:
[rearranged to put the most critical point first]
Siddharth Shah wrote:
I don't have any backup available, Is there any way to fix this ?
I *strongly* recommend that you shut down the database and take a
file copy of the whole data tree (everything under wha
[rearranged to put the most critical point first]
Siddharth Shah wrote:
> I don't have any backup available, Is there any way to fix this ?
I *strongly* recommend that you shut down the database and take a
file copy of the whole data tree (everything under what -D points to
on the server sta
Thanks Kevin.
Yes, I installed 8.4.3 then I have found that DDL and DML statements
were getting failed to execute in some distributions
So that's why taken call for reindexing
What can be the method to verify that it's a database corruption ?
xdb=# \dt;
ERROR: index "pg_class_relname_nsp_
Siddharth Shah wrote:
> * fsync is off*
If you are running the database with fsync off and there is any sort
of unusual termination, your database will probably be corrupted. I
recommend restoring from your last good backup. If you don't have
one, recovery is going to be painful; I recommend
"Campbell, Lance" writes:
> Thanks. Do I add the following to the postgresql.conf file?
> ssl_renegotiation_limit = 0
Right. The variable won't be listed in your existing file, likely,
because that option is new as of last month's updates.
regards, tom lane
--
Sent vi
28, 2010 3:47 PM
To: Campbell, Lance
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Error in PostgreSQL log
"Campbell, Lance" writes:
> PostgreSQL: 8.4.3
> I found the following in my error log:
> LOG: SSL error: unsafe legacy renegotiation disabled
> Anyone have a clu
"Campbell, Lance" writes:
> PostgreSQL: 8.4.3
> I found the following in my error log:
> LOG: SSL error: unsafe legacy renegotiation disabled
> Anyone have a clue what this means?
It means your SSL library is maintained by someone with a clue ;-).
It's dealing with CVE-2009-3555 without simply b
: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] ERROR: cannot read block 15157 of hp_tran: Success
Khangelani Gama writes:
> Please bear with us we are in process of upgrade but many servers are still
> using version 7.3.4 of PostgreSQL running on RedHat5
Egad...
> A certain table se
Khangelani Gama writes:
> Please bear with us we are in process of upgrade but many servers are still
> using version 7.3.4 of PostgreSQL running on RedHat5
Egad...
> A certain table seems to be corrupt when trying to select everything from
> this table, it throws out an error. See the error b
On Tue, Mar 30, 2010 at 04:16, Mike Williams wrote:
> Thanks Alex, good to know I've not screwed up the kernel somehow.
>
> I've been using 2.6.32 with grsecurity-2.1.14-2.6.32.9-201002231820 applied.
Looks like the first instance I had of this problem was with
2.6.31.1-rc1-grsec. I know I tried
On Monday 29 March 2010 20:26:08 Alex Hunsaker wrote:
> > Test are para-virt VMs with "regular" kernels, production are real
> > machines with hardened kernels (grsec+pax).
>
> Ive seen this error on a few boxes around here, using a non grsec
> kernel fixes it. I never bothered to report it becaus
On Sun, Mar 28, 2010 at 16:27, Mike Williams wrote:
> Test are para-virt VMs with "regular" kernels, production are real
> machines with hardened kernels (grsec+pax).
Ive seen this error on a few boxes around here, using a non grsec
kernel fixes it. I never bothered to report it because I cant
r
Good
morning
You
have to revise the base folder to create postgres when you perform the
initial installation and verify the relation fallanado that I spend And
it turned out he had a folder in C: \ Program Files \ PostgreSQL \ 8.2 \
data \ base folder exists the number 1, this
is where the
On Sun, March 28, 2010 8:49 pm, Tom Lane wrote:
>> The server is Gentoo, and I don't have an identical server to use. This
>> machines HA partner is staying at 8.3.5 until we're completely and
>> entirely sure 8.3.10 works right.
>
> I wasn't really suggesting that you need an *identical* machine.
"Mike Williams" writes:
> The "target block" stays the same for extended periods, but does change.
Fascinating. Don't know what it means, but it's fascinating.
> Where does the 1663 number come from?
> /743352/743420 is a real file, but I don't have any file 1663.
1663 is the OID of the pg_def
On Sun, March 28, 2010 7:20 pm, Tom Lane wrote:
> Mike Williams writes:
>> ERROR: could not open segment 1 of relation 1663/743352/743420 (target
>> block
>> 2171336): No such file or directory
>> CONTEXT: SQL statement "SELECT day FROM min_stats WHERE day<= $1 AND
>> unique_ip=-1 ORDER BY day
Mike Williams writes:
> We upgraded from 8.3.5 to 8.3.9 yesterday, after an extended period of
> testing, to 8.3.10 today in hope of fixing it, and we're getting the
> following
> error on occasion.
> ERROR: could not open segment 1 of relation 1663/743352/743420 (target block
> 2171336): No
On Thu, 2010-03-18 at 21:23 -0400, Vitaly Burshteyn wrote:
> Host key verification failed.
>
> I know there is nothing wrong with my host key as I can move between
> the servers with out any issues.
Host key != ssh key.
You can easily reproduce this issue by trying to ssh from master to
slave ser
Please chek again and inform me.thanx for the information.
On 12/28/09, Shruthi A wrote:
> On 12/28/09, Premila Devi wrote:
>>
>> select sum(alq.quantity + alq.locked), category.id, alq.assetStatus.name
>>
>> from AssetLocationQuantity alq inner join alq.asset asset inner join
> asset.assetModel
Secondly this is not the right group to address such problems. This is an
sql-syntax related issue. You should address this question to
pgsql-gene...@postgresql.org or better still, pgsql-...@postgresql.org.
Thanks,
Shruthi
On 12/28/09, Shruthi A wrote:
>
> On 12/28/09, Premila Devi wrote:
>
On 12/28/09, Premila Devi wrote:
>
> select sum(alq.quantity + alq.locked), category.id, alq.assetStatus.name
>
> from AssetLocationQuantity alq inner join alq.asset asset inner join
asset.assetModel model inner join model.category category
>
> group by category, alq.assetStatus.name;
>
> ERROR:
Hi,
what is "alq.assetStatus " and " alq.asset"? Is it a table name?
syntax for referring column is "tablename.columnname" .
We need to use column names in the group by clause.
I think you need to check query syntax and you have not used assetStatus
table in the query.
On Mon, 2009-12-28 a
Strange - seems to have sorted itself out.
I turned off a scheduled vacuum of the table and within a few minutes I
sorted itself out.
I have reduced the frequency of the vacuuming task which is being
carried out via pgagent.
From: Benjamin Krajmalnik
Sent: Monday, December 14, 2009 12:28
Additional info:
When I perform a vacuum full, this is the information I am getting:
INFO: vacuuming "public.tblksaura"
INFO: "tblksaura": found 89 removable, 238907 nonremovable row versions
in 59808 pages
DETAIL: 200792 dead row versions cannot be removed yet.
Nonremovable row versi
idris khanafi writes:
> When I running pg_dump i have error
> pg_dump: Error message from server: ERROR: MemoryContextAlloc: invalid
> request size 4294967293
> pg_dump: The command was: FETCH 100 FROM _pg_dump_cursor
Looks like a corrupted-data problem to me. You might try not using
the -d/-D
Boa Tarde Venkat,
Acredito que o erro está na sua chamada da função dblink_exec:
SELECT * FROM dblink_exec('hostname=sys2ip dbname=testB user=postgres
password=postgres','INSERT INTO emp NEW.*');
Pelo fato de você estar passando o NEW dentro de aspas, o postgres está
entendendo que é uma string
Kenneth Marshall wrote:
I just thought of something, would running an older release of pgadmin
cause this error?
I have just restored a DB from 8.3.5 to 8.4.0 and I just
received the error:
ERROR: column "reltriggers" does not exist at character 41
STATEMENT: SELECT relhasindex, relkind,
I just thought of something, would running an older release of pgadmin
cause this error?
Cheers,
Ken
On Wed, Aug 05, 2009 at 06:29:07PM -0500, Kenneth Marshall wrote:
> Dear PostgreSQL admins.
>
> I have just restored a DB from 8.3.5 to 8.4.0 and I just
> received the error:
>
> ERROR: column
Cc: Alvaro Herrera; pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] Error in creating the backend query
>
> I wish that were the case.
> I am running 8.3.7 built from the FreeBSD ports.
> All insertions and updates to that table (or any others) are done
> exclusively through tha
"Benjamin Krajmalnik" writes:
> So the plpgsql stored procedure is definitely the source.
If you want to convince me of that you need to provide a *self
contained* demonstration. An out-of-context procedure definition
isn't helpful because I can't test it.
regards, tom l
PM
> To: Benjamin Krajmalnik
> Cc: Alvaro Herrera; pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] Error in creating the backend query
>
> "Benjamin Krajmalnik" writes:
> > Below is the full stored procedure.
>
> All I can do is repeat that plpgsql does
"Benjamin Krajmalnik" writes:
> Below is the full stored procedure.
All I can do is repeat that plpgsql does not behave that way. It never
has AFAIR, and it most definitely doesn't in any version new enough to
recognize the COST option to CREATE FUNCTION (ie, 8.3 and up). In fact,
I don't belie
e, timestamp
without time zone, integer, character varying, character varying,
integer) OWNER TO postgres;
> -Original Message-
> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
> Sent: Wednesday, July 29, 2009 3:31 PM
> To: Alvaro Herrera
> Cc: Benjamin Krajmalnik; pg
Benjamin Krajmalnik wrote:
> I tried it with both on and off, and it did not make a difference.
Please show a complete example.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
--
Sent via pgsql-
Alvaro Herrera writes:
> Benjamin Krajmalnik wrote:
>> Please note the "lasteventsource is null" instead of "lasteventsource =
>> null" which is being generated when the value of x_eventsource is null.
> Do you have transform_null_equals set?
Even if he did, that wouldn't affect the source form
I tried it with both on and off, and it did not make a difference.
> -Original Message-
> From: Alvaro Herrera [mailto:alvhe...@commandprompt.com]
> Sent: Wednesday, July 29, 2009 3:20 PM
> To: Benjamin Krajmalnik
> Cc: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN]
Benjamin Krajmalnik wrote:
> update tblksalerts set cleartime = '2009-07-29 10:49:50'::TIMESTAMP,
> laststatusid = 7::INTEGER, lastreplytext = '0'::VARCHAR, lasttesttime =
> '2009-07-29 10:49:50'::TIMESTAMP, lasteventsource is NULL::VARCHAR,
> lasteventid is NULL::INTEGER, replyval = 0::REAL, tren
RANT ALL ON TABLE classification_guide_jobs TO postgres;
69
70
71 --
72 -- PostgreSQL database dump complete
73 --
-Original Message-
From: Scott Marlowe [mailto:scott.marl...@gmail.com]
Sent: Wednesday, June 17, 2009 10:10 AM
To: Marc Fromm
Cc: pgsql-admin@postgresql.org
Subject: Re: [A
On Wed, Jun 17, 2009 at 10:51 AM, Marc Fromm wrote:
> I am receiving this error when I try to add new records:
>
> INSERT INTO "public"."classification_guide_cats" ("id", "cat_title") VALUES
> (nextval(('"classification_guide_cat_id_seq"'::text)::regclass), 'temp')
>
> SQL error:
>
> ERROR: duplic
What about your mantainance_mem parameter in postgresql.conf? If it is
very high, are you sure do you have free memory enough?
I had a similar problem two weeks ago due to this issue and I had to low
effective_cache_size in order to get memory enough for vacuum process.
_
De: Ygor Degani
On Mon, Jan 5, 2009 at 6:17 AM, Ygor Degani wrote:
> I use postgres-8.3.5. My database has 168 GB in size. Whenever i try to do
> vacuum full happens the following error:
>
> WARNING: terminating connection because of crash of another server process
> DETAIL: The postmaster has commanded this se
1 - 100 of 372 matches
Mail list logo
