Chris Travers wrote:
> John R Pierce wrote:
> I often find in those cases it is a choice between vacuum full
> and dumpall/initdb/reload/analyze.
Way back in the 8.1 days I often found CLUSTER to be my best option
-- as long as I had room enough for a second copy (without the
bloat) while i
On Wed, Oct 9, 2013 at 7:04 PM, John R Pierce wrote:
> On 10/8/2013 8:35 AM, Chris Travers wrote:
>
>> First, while vacuum is usually preferred to vacuum full, in this case, I
>> usually find that vacuum full clears up enough cruft to be worth it (not
>> always, but especially if you are also hav
On 10/8/2013 8:35 AM, Chris Travers wrote:
First, while vacuum is usually preferred to vacuum full, in this case,
I usually find that vacuum full clears up enough cruft to be worth it
(not always, but especially if you are also having performance issues).
IIRC, vacuum full was pretty broken i
On 10/08/2013 09:03 AM, David Johnston wrote:
postgres -D /var/lib/pgsql/data patnadbold < fix.sql
What the heck is the point of feeding "VACUUM FULL;" into the standard input
of the postgres command? "postgres" simply starts the server, it does not
execute arbitrary SQL. Once the database
> postgres -D /var/lib/pgsql/data patnadbold < fix.sql
What the heck is the point of feeding "VACUUM FULL;" into the standard input
of the postgres command? "postgres" simply starts the server, it does not
execute arbitrary SQL. Once the database is started you want to use "psql"
- either inter
First, while vacuum is usually preferred to vacuum full, in this case, I
usually find that vacuum full clears up enough cruft to be worth it (not
always, but especially if you are also having performance issues).
Secondly I would recommend using the vacuumdb command from the shell
instead of psql
On Tue, Oct 8, 2013 at 8:25 AM, shailesh singh wrote:
> yes i am executing psql to connect to this database.
>
> su - postgres
> psql patnadbold
>
..and then what? Does it immediately throw an error stating that you must
issue a VACUUM?
yes i am executing psql to connect to this database.
su - postgres
psql patnadbold
On Tue, Oct 8, 2013 at 8:48 PM, bricklen wrote:
>
>
>
> On Tue, Oct 8, 2013 at 8:13 AM, shailesh singh wrote:
>
>>
>> On Tue, Oct 8, 2013 at 8:36 PM, bricklen wrote:
>>
>>>
>>> On Tue, Oct 8, 2013 at 8
On Tue, Oct 8, 2013 at 8:13 AM, shailesh singh wrote:
>
> On Tue, Oct 8, 2013 at 8:36 PM, bricklen wrote:
>
>>
>> On Tue, Oct 8, 2013 at 8:03 AM, shailesh singh wrote:
>>
>>> HINT: To avoid a database shutdown, execute a full-database VACUUM in
>>> "patnadbold".
>>> ERROR: could not access status
On Tue, Oct 08, 2013 at 08:06:50AM -0700, bricklen wrote:
> On Tue, Oct 8, 2013 at 8:03 AM, shailesh singh wrote:
>
> > HINT: To avoid a database shutdown, execute a full-database VACUUM in
> > "patnadbold".
> > ERROR: could not access status of transaction 33011
> > DETAIL: could not open file "p
On 10/08/2013 08:03 AM, shailesh singh wrote:
Dear all,
First of all i wish to share actual error meassge,
Below are the queries i had executed on the terminal on my server
-bash-3.2$ touch fix.sql
-bash-3.2$ echo "VACUUM FULL;" > fix.sql
-bash-3.2$ postgres -D /var/lib/pgsql/data patnadbold
On Tue, Oct 8, 2013 at 8:03 AM, shailesh singh wrote:
> HINT: To avoid a database shutdown, execute a full-database VACUUM in
> "patnadbold".
> ERROR: could not access status of transaction 33011
> DETAIL: could not open file "pg_clog/": No such file or directory
> exit
>
>
> After this i am a
Dear all,
First of all i wish to share actual error meassge,
Below are the queries i had executed on the terminal on my server
-bash-3.2$ touch fix.sql
-bash-3.2$ echo "VACUUM FULL;" > fix.sql
-bash-3.2$ postgres -D /var/lib/pgsql/data patnadbold < fix.sql
WARNING: database "patnadbold" must be
Adrian Klaver-3 wrote
> On 10/08/2013 03:55 AM, shailesh singh wrote:
>> I had got this message while running vacuum full from backend . Now My
>> database is not starting , Help pls.
>>
>> backend> vacuum full debug;
>> WARNING: database "debug" must be vacuumed within 99 transactions
>> HINT
On 10/08/2013 03:55 AM, shailesh singh wrote:
I had got this message while running vacuum full from backend . Now My
database is not starting , Help pls.
backend> vacuum full debug;
WARNING: database "debug" must be vacuumed within 99 transactions
HINT: To avoid a database shutdown, execut
I had got this message while running vacuum full from backend . Now My
database is not starting , Help pls.
backend> vacuum full debug;
WARNING: database "debug" must be vacuumed within 99 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in
"debug".
ERROR: rel
On 2012-01-06, Phoenix Kiula wrote:
> On Fri, Jan 6, 2012 at 6:53 PM, Steve Crawford
> wrote:
> Thanks Steve.
>
> The file has 350 million lines. Sed, Awk etc are a little painful when
> the file is 18GB witht hat many lines.
On files of that size they're a lot nicer than an interactive editor
On Fri, Jan 6, 2012 at 10:38 PM, John R Pierce wrote:
> you should check your attitude at the door. this isn't Microsoft Pay per
> Incident Tech Support.
I saw the door. Found some other attitudes that were allowed to be let
in. Like asking me to write my own patch. You see, attitudes come in
On 01/06/12 5:33 PM, Phoenix Kiula wrote:
> http://pgloader.projects.postgresql.org/
Sorry. That I already did.
But where's the config file? How to configure the config file?
Where's the simple doc (not on that ugly PGFoundry website, I mean in
English that people can understand what to do, wi
On Fri, Jan 6, 2012 at 8:19 PM, Adrian Klaver wrote:
> On Friday, January 06, 2012 4:16:09 pm Phoenix Kiula wrote:
>> On Fri, Jan 6, 2012 at 6:54 PM, Adrian Klaver
>> wrote:
>> > Try:
>> > copy vl from 'data.txt' WITH CSV DELIMITER '|';
>>
>> Doesn't work. Can't see what the different in CSV is
On Friday, January 06, 2012 4:16:09 pm Phoenix Kiula wrote:
> On Fri, Jan 6, 2012 at 6:54 PM, Adrian Klaver wrote:
> > Try:
> > copy vl from 'data.txt' WITH CSV DELIMITER '|';
>
> Doesn't work. Can't see what the different in CSV is from a text file.
> Same errors are thrown.
>
> > If that doesn
On 01/06/2012 03:55 PM, Phoenix Kiula wrote:
...
In general, when you have data scrubbing issues like this, grep/sed/awk/...
are your friends. Clean it up then import it.
Thanks Steve.
The file has 350 million lines. Sed, Awk etc are a little painful when
the file is 18GB witht hat many lines.
On Fri, Jan 6, 2012 at 6:54 PM, Adrian Klaver wrote:
>
> Try:
> copy vl from 'data.txt' WITH CSV DELIMITER '|';
Doesn't work. Can't see what the different in CSV is from a text file.
Same errors are thrown.
> If that doesn't work take a look at pgloader:
> http://pgfoundry.org/projects/pgloade
On 01/06/2012 03:12 PM, Phoenix Kiula wrote:
...
Sounds like you are using statement pooling - every statement can be
assigned to a different server connection. You may need transaction pooling
or session pooling:
http://pgbouncer.projects.postgresql.org/doc/usage.html
Thanks Steve. YES! I c
On Fri, Jan 6, 2012 at 6:53 PM, Steve Crawford
wrote:
> On 01/06/2012 03:42 PM, Phoenix Kiula wrote:
>>
>> On Fri, Jan 6, 2012 at 6:20 PM, Adrian Klaver
>> wrote:
>>
>>> http://www.postgresql.org/docs/9.0/interactive/sql-copy.html
>>>
>>> Search for
>>> NULL
>>
>>
>>
>> Thanks Adrian.
>>
>> Witho
On 01/06/2012 03:42 PM, Phoenix Kiula wrote:
On Fri, Jan 6, 2012 at 6:20 PM, Adrian Klaver wrote:
http://www.postgresql.org/docs/9.0/interactive/sql-copy.html
Search for
NULL
Thanks Adrian.
Without examples, it's hard to predict syntax. If the value after a
pipe is missing altogether, I
On 01/06/2012 03:42 PM, Phoenix Kiula wrote:
On Fri, Jan 6, 2012 at 6:20 PM, Adrian Klaver wrote:
http://www.postgresql.org/docs/9.0/interactive/sql-copy.html
Search for
NULL
Thanks Adrian.
Without examples, it's hard to predict syntax. If the value after a
pipe is missing altogether, I s
On Fri, Jan 6, 2012 at 6:20 PM, Adrian Klaver wrote:
> http://www.postgresql.org/docs/9.0/interactive/sql-copy.html
>
> Search for
> NULL
Thanks Adrian.
Without examples, it's hard to predict syntax. If the value after a
pipe is missing altogether, I suppose the missing value is "\n"
(newline
On 01/06/2012 03:12 PM, Phoenix Kiula wrote:
On Fri, Jan 6, 2012 at 4:24 PM, Steve Crawford
wrote:
On 01/06/2012 01:11 PM, Phoenix Kiula wrote:
Thanks Steve. YES! I changed it to transaction pooling and now it works.
Another problem through.
I need to COPY a huge text file into a table,
On Fri, Jan 6, 2012 at 4:24 PM, Steve Crawford
wrote:
> On 01/06/2012 01:11 PM, Phoenix Kiula wrote:
>>
>> On Fri, Jan 6, 2012 at 11:46 AM, Tom Lane wrote:
>>>
>>> Phoenix Kiula writes:
Hi. I'm using Postgresql 9.0.5, and the connection is made via
pgbouncer.
>>>
>>> Perhaps pgbou
Marko Kreen writes:
> On Fri, Jan 6, 2012 at 11:24 PM, Steve Crawford
> wrote:
>> On 01/06/2012 01:11 PM, Phoenix Kiula wrote:
>>> How can I make sure pgbouncer takes it all in the same session? I also
>>> tried the two commands within a transaction.
>> Sounds like you are using statement poolin
On Fri, Jan 6, 2012 at 11:24 PM, Steve Crawford
wrote:
> On 01/06/2012 01:11 PM, Phoenix Kiula wrote:
>>
>> On Fri, Jan 6, 2012 at 11:46 AM, Tom Lane wrote:
>>>
>>> Phoenix Kiula writes:
Hi. I'm using Postgresql 9.0.5, and the connection is made via
pgbouncer.
>>>
>>> Perhaps pgbo
On 01/06/2012 01:11 PM, Phoenix Kiula wrote:
On Fri, Jan 6, 2012 at 11:46 AM, Tom Lane wrote:
Phoenix Kiula writes:
Hi. I'm using Postgresql 9.0.5, and the connection is made via pgbouncer.
Perhaps pgbouncer is redirecting the second command to a different
session?
Thanks Tom. I'm in the
On Fri, Jan 6, 2012 at 11:46 AM, Tom Lane wrote:
> Phoenix Kiula writes:
>> Hi. I'm using Postgresql 9.0.5, and the connection is made via pgbouncer.
>
> Perhaps pgbouncer is redirecting the second command to a different
> session?
>
Thanks Tom. I'm in the exact same session in my terminal, an
Tom Lane wrote:
> Phoenix Kiula writes:
>> Hi. I'm using Postgresql 9.0.5, and the connection is made via pgbouncer.
>
> Perhaps pgbouncer is redirecting the second command to a different
> session?
This may be OT, but are temp tables also removed when setting a new session
authorization?
Bosco
Phoenix Kiula writes:
> Hi. I'm using Postgresql 9.0.5, and the connection is made via pgbouncer.
Perhaps pgbouncer is redirecting the second command to a different
session?
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make
Hi. I'm using Postgresql 9.0.5, and the connection is made via pgbouncer.
I create a temporary table, and then want to import data into this
table via a COPY command. Yet, this just created table is not being
recognized. What's up?
>From my terminal:
mydb=#
mydb=# create temporary table vl (
On Saturday 07 May 2011, John R Pierce elucidated thus:
> On 05/07/11 6:08 AM, Bob Wilson wrote:
> > Hello
> > This is Bob and I will like to order ( Indexing Table )Do get back
> > to me with the types and cost for the ones you do carry and let me
> > know if there is an extra cost when using visa
On 05/07/11 6:08 AM, Bob Wilson wrote:
Hello
This is Bob and I will like to order ( Indexing Table )Do get back to
me with the types and cost for the ones you do carry and let me know
if there is an extra cost when using visa or master Card.Kindly get
back to me with your name Are you the sales
Hello
This is Bob and I will like to order ( Indexing Table )Do get back to
me with the types and cost for the ones you do carry and let me know
if there is an extra cost when using visa or master Card.Kindly get
back to me with your name Are you the sales manager or the Owner?
Regards
Bob Wil
On Sun, Dec 12, 2010 at 09:49:52PM -0800, savio rodriges wrote:
> Hello,
>
> We are facing very HIGH memory utilization on postgreSQL server and need help.
which number from all of what's below is making you worried?
Best regards,
depesz
--
Linkedin: http://www.linkedin.com/in/depesz / blog
Hello Savio,
> top - 21:43:35 up 55 days, 8:07, 4 users, load average: 0.05,
> 0.25, 0.17 Tasks: 257 total, 1 running, 256 sleeping, 0 stopped,
> 0 zombie Cpu(s): 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa,
> 0.0%hi, 0.0%si, 0.0%st Mem: 8165696k total, 7943160k used,
> 222536k free,
On Mon, Dec 13, 2010 at 4:49 PM, savio rodriges wrote:
> Hello,
>
> We are facing very HIGH memory utilization on postgreSQL server and need
> help.
>
> Mem: 8165696k total, 7943160k used, 222536k free, 282044k buffers
> Swap: 8385920k total, 112828k used, 8273092k free, 4793732k cach
On Mon, Dec 13, 2010 at 8:49 AM, savio rodriges wrote:
> Hello,
>
> We are facing very HIGH memory utilization on postgreSQL server and need help.
>
> Below are details of PostgreSQL server,
>
> ===
> MemTotal: 8165696 kB
Hello,
We are facing very HIGH memory utilization on postgreSQL server and need help.
Below are details of PostgreSQL server,
===
MemTotal: 8165696 kB
CpuTotal: 8
===
AI Rumman writes:
> The function call "pg_catalog.pg_encoding_to_char(d.encoding)" somehow makes
> the Pgpool hang in SSL mode.
pg_encoding_to_char returns type "name", maybe that's somehow confusing
pgpool? Although I seriously doubt there's any connection to SSL mode.
I am using Pgpool II 2.3.3 with Postgresql 8.3.8.
When I use command \l at postgresql client the query is working perfectly.
But if I used the command from pgpool II client which is connected with
postgresql in ssl mode, it gets hang.
Again if I use the command from pgpool II client in non-ssl m
Venkat wrote:
> In postgre, when i am trying to give alias name in update
> statement like below -
>
> -
> update mytable x
> set x.name = 'asdf'
> where x.no = 1
> ---
>
>
> is giving error - mytable is not having col x.
>
> We
On 09/03/2010 13:51, venkatra...@tcs.com wrote:
> Hello,
>
> In postgre, when i am trying to give alias name in update statement like
> below -
>
> -
> update mytable x
> set x.name = 'asdf'
> where x.no = 1
> ---
Leave leave off the
On Tuesday 09 March 2010 5:51:31 am venkatra...@tcs.com wrote:
> Hello,
>
> In postgre, when i am trying to give alias name in update statement like
> below -
>
> -
> update mytable x
> set x.name = 'asdf'
> where x.no = 1
> ---
>
> is giv
Hello,
In postgre, when i am trying to give alias name in update statement like
below -
-
update mytable x
set x.name = 'asdf'
where x.no = 1
---
is giving error - mytable is not having col x.
We have migrated code from oracle to pos
Hmm would this be a bad time to ask for PostGres 1.0 support?
On Fri, Oct 16, 2009 at 1:55 PM, Jeff Davis wrote:
> On Fri, 2009-10-16 at 11:26 +0100, Neha Patel wrote:
>> We are running with postgres sql 7.3.2. We were trying to create an
>> index on a big table. The create index command ran for
On Fri, 2009-10-16 at 11:26 +0100, Neha Patel wrote:
> We are running with postgres sql 7.3.2. We were trying to create an
> index on a big table. The create index command ran for nearly 5 hours
> at which point we decided to interrupt it. Since this was interrupted,
> any operations attempted on t
Neha Patel wrote:
Hi,
We are running with postgres sql 7.3.2. We were trying to...
well, right off the bat, thats a -really- old version. Release notes
say February 2003. 7.3 was updated to 7.3.21, and we're currently on
8.4 (while still supporting 8.3, 8.2, 8.1, and 7.4).There
Hi David,
Many thanks for your reply. After good 10 hours of work we managed to
restore from a backup.
Regards
Neha>
-Original Message-
From: David Fetter [mailto:da...@fetter.org]
Sent: 16 October 2009 17:28
To: Neha Patel
Cc: pgsql-general@postgresql.org
Subject: Re: [GENE
On Fri, Oct 16, 2009 at 11:26:40AM +0100, Neha Patel wrote:
> Hi,
>
> We are running with postgres sql 7.3.2.
Whatever you thought your most urgent priority was, it's actually
getting your database off of a major version of PostgreSQL, 7.3, whose
end-of-life was well over a year ago.
Your secon
On Fri, Oct 16, 2009 at 11:26 AM, Neha Patel wrote:
> Hi,
>
>
>
> We are running with postgres sql 7.3.2. We were trying to create an index
> on a big table. The create index command ran for nearly 5 hours at which
> point we decided to interrupt it. Since this was interrupted, any
> operations
Hi,
We are running with postgres sql 7.3.2. We were trying to create an
index on a big table. The create index command ran for nearly 5 hours at
which point we decided to interrupt it. Since this was interrupted, any
operations attempted on the table on which the index was being created
gives fol
I copied back to list as your chances of getting an answer are greater.
On Sunday 01 February 2009 10:15:04 pm you wrote:
> The Postgres version is PostgreSQL version 8.3.4.
> OS type - Windows XP Proffesional Version 2002
> Our application is a client server Java application which collects data
On Sunday 01 February 2009 12:38:21 am Preethi Valsalan wrote:
> Hi
>
> I am working on an application where Postgresql is used as the db. I have a
> trigger and three functions running on that trigger. The data in db is
> updated by a thread each 1 minute continuously.
>
> I kept my application r
Hi
I am working on an application where Postgresql is used as the db. I have a
trigger and three functions running on that trigger. The data in db is
updated by a thread each 1 minute continuously.
I kept my application running for 2 days and on runtime Postgres stopped
running. But when I r
"A. Kretschmer" <[EMAIL PROTECTED]> writes:
> am Tue, dem 18.11.2008, um 11:25:16 -0300 mailte Gustavo Rosso folgendes:
>> banco=> create table tabla (x integer);
>> NOTICE: CREATE TABLE / UNIQUE will create implicit index
>> "tabla_oid_idx" for table "tabla"
>> *ERROR: must be owner of relat
On Tue, Nov 18, 2008 at 11:46:07AM -0300,
Gustavo Rosso <[EMAIL PROTECTED]> wrote
a message of 68 lines which said:
> PostgreSQL 7.4 informix1.8 on i686-pc-linux-gnu, compiled by GCC gcc
> (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)
> Is it old version?
It is still in Debian "stable"
Andreas, my version is:
select version();
PostgreSQL 7.4 informix1.8 on i686-pc-linux-gnu, compiled by GCC gcc
(GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)
Is it old version?
Can to be the reason for my problem?
A. Kretschmer escribió:
am Tue, dem 18.11.2008, um 11:25:16 -0300 mailte
am Tue, dem 18.11.2008, um 11:25:16 -0300 mailte Gustavo Rosso folgendes:
> People of world, help help please.
> I created a DB with super-user postgres, I give all privileges to DB
> (banco is my DB)
> GRANT ALL ON DATABASE banco TO PUBLIC;
> GRANT CREATE ON DATABASE banco TO PUBLIC
>
> But oth
People of world, help help please.
I created a DB with super-user postgres, I give all privileges to DB
(banco is my DB)
GRANT ALL ON DATABASE banco TO PUBLIC;
GRANT CREATE ON DATABASE banco TO PUBLIC
But other users can't create tables in this DB
ERROR:
banco=> create table tabla (x integer)
On 25/09/2007, Michael Fuhr <[EMAIL PROTECTED]> wrote:
> > How can I remove characters that form a part of regular expressions?
>
> Why do you want to do that?
Because these values were inserted into the DB due to a faulty
application. So cleansing was called for.
I just ended up doing it with r
On Tue, Sep 25, 2007 at 01:36:26PM +0800, Phoenix Kiula wrote:
> How can I remove characters that form a part of regular expressions?
Why do you want to do that?
> I would like to remove all instances of the following characters:
>
> [
> ]
> \
> +
test=> select id, t, regexp_replace(t, e'[[
Hi,
How can I remove characters that form a part of regular expressions? I
would like to remove all instances of the following characters:
[
]
\
+
Given that these all mean something in regexp, I am trying to prefix
them with a backslash, but it doesn't work. I tried the following:
update T
On 31/08/2007, Jeff Davis <[EMAIL PROTECTED]> wrote:
> On Fri, 2007-08-31 at 22:34 +0800, Phoenix Kiula wrote:
> > On 31/08/2007, Josh Tolley <[EMAIL PROTECTED]> wrote:
> > > On 8/31/07, Zoltan Boszormenyi <[EMAIL PROTECTED]> wrote:
> > > > Phoenix Kiula írta:
> >
> > > In addition to what others h
On Fri, 2007-08-31 at 22:34 +0800, Phoenix Kiula wrote:
> On 31/08/2007, Josh Tolley <[EMAIL PROTECTED]> wrote:
> > On 8/31/07, Zoltan Boszormenyi <[EMAIL PROTECTED]> wrote:
> > > Phoenix Kiula írta:
>
> > In addition to what others have already said, when things calm down
> > you should consider
On Aug 31, 2007, at 8:35 AM, Phoenix Kiula wrote:
Thanks everyone. Yes, /var was full because of the backups that're
going there.
Database is back working.
It was my backup script. It is set to save a daily backup to the /var/
folder, which is not clever. I'll change it to be in the "backup
On 31/08/2007, Josh Tolley <[EMAIL PROTECTED]> wrote:
> On 8/31/07, Zoltan Boszormenyi <[EMAIL PROTECTED]> wrote:
> > Phoenix Kiula írta:
> In addition to what others have already said, when things calm down
> you should consider implementing some sort of monitoring system that
> is configured to
On 31/08/2007, Zoltan Boszormenyi <[EMAIL PROTECTED]> wrote:
> Phoenix Kiula írta:
> > I am getting this message when I start the DB:
> >
> >
> > psql: FATAL: could not access status of transaction 0
> > DETAIL: Could not write to file "pg_subtrans/01F8" at offset 221184:
> > No space left on dev
On 8/31/07, Zoltan Boszormenyi <[EMAIL PROTECTED]> wrote:
> Phoenix Kiula írta:
> > I am getting this message when I start the DB:
> >
> >
> > psql: FATAL: could not access status of transaction 0
> > DETAIL: Could not write to file "pg_subtrans/01F8" at offset 221184:
> > No space left on device
Phoenix Kiula írta:
I am getting this message when I start the DB:
psql: FATAL: could not access status of transaction 0
DETAIL: Could not write to file "pg_subtrans/01F8" at offset 221184:
No space left on device.
What is this about and how do I solve this? A "df -h" on my system shows thi
On 8/31/07, Phoenix Kiula <[EMAIL PROTECTED]> wrote:
> I am getting this message when I start the DB:
>
>
> psql: FATAL: could not access status of transaction 0
> DETAIL: Could not write to file "pg_subtrans/01F8" at offset 221184:
> No space left on device.
>
>
> What is this about and how do I
Looks like you're out of disk space on:
/dev/sda2 ext39.9G 9.5G 0 100% /var
is this where your database resides?
Phoenix Kiula wrote:
> I am getting this message when I start the DB:
>
>
> psql: FATAL: could not access status of transaction 0
> DETAIL: Could not write to file "
Phoenix Kiula wrote:
I am getting this message when I start the DB:
psql: FATAL: could not access status of transaction 0
DETAIL: Could not write to file "pg_subtrans/01F8" at offset 221184:
No space left on device.
What is this about and how do I solve this? A "df -h" on my system shows th
I am getting this message when I start the DB:
psql: FATAL: could not access status of transaction 0
DETAIL: Could not write to file "pg_subtrans/01F8" at offset 221184:
No space left on device.
What is this about and how do I solve this? A "df -h" on my system shows this:
FilesystemTyp
Hi,
We have excellent and urgent job opening for PostgreSQL DBA with one
of our esteemed client in Pune/ Bangalore.
Skillset : PostgreSQL DBA
Experience : 5 - 7 yrs
Location : Pune/ Bangalore.
If interested, please send me your updated resume in MS word format
along with the CTC de
Hi,
We have excellent and urgent job opening for PostgreSQL DBA with one
of our esteemed client in Pune/ Bangalore.
Skillset : PostgreSQL DBA
Experience : 5 - 7 yrs
Location : Pune/ Bangalore.
If interested, please send me your updated resume in MS word format
along with the CTC de
On Fri, 2007-02-23 at 17:14 -0500, Merlin Moncure wrote:
> BUG: spinlock recursion CPU0 postmaster...not tainted.
> Has anybody seen any problem like this or have any suggestions about
> possible resolution...should I be posting to the LKML?
AFAIR (+ some quick Googling), this is related to
Ok,
This may the wrong place to look for answers to this, but I figured it
couldn't hurt...so here goes:
On friday we upgraded a critical backend server to postgresql 8.2
running on fedora core 4. Since then we have received three kernel
panics during periods of moderate to high load (twice dur
Emanuele Rocca wrote:
-- Start of PGP signed section.
> Hello Tom,
>
> * Tom Lane <[EMAIL PROTECTED]>, [2006-10-06 15:16 -0400]:
> > Um, were you running with full_page_writes off? Bad idea in 8.1 :-( ...
>
> The manual [1] says that full_page_writes is ignored and always treated
> as if it was
Hello Tom,
* Tom Lane <[EMAIL PROTECTED]>, [2006-10-06 15:16 -0400]:
> Um, were you running with full_page_writes off? Bad idea in 8.1 :-( ...
The manual [1] says that full_page_writes is ignored and always treated
as if it was set to on. Is it wrong?
ciao,
ema
[1]
http://www.postgresql.
andy rost <[EMAIL PROTECTED]> writes:
> Our Opteron DB server had a problem with its RAID controller requiring
> an immediate shutdown of our Postgres server (8.1.3 on FreeBSD 6.0
> release number 10). We used kill -QUIT on the postmaster PID.
> 2006-10-06 12:32:40 CDT PANIC: heap_clean_redo: n
Our Opteron DB server had a problem with its RAID controller requiring
an immediate shutdown of our Postgres server (8.1.3 on FreeBSD 6.0
release number 10). We used kill -QUIT on the postmaster PID.
After repairing and rebooting the server we tried to start Postgres and
get the following:
2
rch 24, 2006 1:11 PM
Subject: Re: [GENERAL] URGENT! could not access status of transaction
"Reimer" <[EMAIL PROTECTED]> writes:
pg_dump: ERROR: could not access status of transaction 1768711534
DETAIL: could not open file "/usr/local/pgsql/data/pg_clog/0696": =
Arquivo
"Reimer" <[EMAIL PROTECTED]> writes:
> pg_dump: ERROR: could not access status of transaction 1768711534
> DETAIL: could not open file "/usr/local/pgsql/data/pg_clog/0696": =
> Arquivo ou dire
> t=F3rio n=E3o encontrado
> How is the best way to fix? pg_resetxlog?
resetxlog won't help: you've go
-- Original Message -
> From: Reimer
> To: pgsql-general@postgresql.org
> Sent: Friday, March 24, 2006 10:41 AM
> Subject: [GENERAL] URGENT! could not access status of transaction
>
>
> Hello,
>
> We had some disk problems here and now pg_dump is complaining
I forgot to mention postgreSQL version:
7.4.6
Thanks!
- Original Message -
From:
Reimer
To: pgsql-general@postgresql.org
Sent: Friday, March 24, 2006 10:41
AM
Subject: [GENERAL] URGENT! could not
access status of transaction
Hello,
We had some
Hello,
We had some
disk problems here and now pg_dump is complaining with:
pg_dump: ERROR: could not access status of
transaction 1768711534DETAIL: could not open file
"/usr/local/pgsql/data/pg_clog/0696": Arquivo ou diretório não
encontradopg_dump: SQL command to dump the contents of
Am 2006-03-13 23:58:40, schrieb r irussel:
> Hello Every body:
>
> I have implemented psql version 7.4.2 on Debian linux version 3.2
Where does this PostgreSQL version come from?
And there is NO version 3.2 of Debian GNU/Linux.
Only 3.0 (Woody), 3.1 (Sarge) and maybe 4.0 (Etch).
You should
Why have you asked the same question 3 times in five minutes?
Additional responses below.
[EMAIL PROTECTED] wrote:
> hi all,
>
> i have a web based java application with a postgres db.
>
> now i am trying to generate a temp table which contains all hour
> records for a selected date range. eg. i
Have you considered using a stored proceedure? It seems like it might easily
give you the logic you're after.
http://www.postgresql.org/docs/8.1/static/xplang.html
On Sun, 12 Mar 2006, [EMAIL PROTECTED] wrote:
hi all,
i have a web based java application with a postgres db.
now i am trying t
hi all,
i have a web based java application with a postgres db.
now i am trying to generate a temp table which contains all hour
records for a selected date range. eg. if the user selects 2006-03-14
as from and 2006-03-14 as to, the system should insert 24 hour records
with their individual time
r irussel wrote:
Hello Every body:
I have implemented psql version 7.4.2 on Debian linux version 3.2
and it was running very well. At this moment it is being crashed when
executing a single select statement. Details are mentionded as
follows:
You really should be running something later than 7
Hello Every body: I have implemented psql version 7.4.2 on Debian linux version 3.2 and it was running very well. At this moment it is being crashed when executing a single select statement. Details are mentionded as follows: DB Dump size before this problem is arised: 95 MB DB ENCODING
> Hi all,
> I am trying to create an installable for my metalscan java
> application. Here are the specs:- I have created the
> installable using GKsetup(Gkware.com) a third party tool. I
> am using Postgresql 8.0.2 as my database for my Java
> application(metalscan). When the setup executable
1 - 100 of 149 matches
Mail list logo
