decide whether to wait for 8.2 to become available. Some of the new
features are rather enticing.
I'm not asking for a promised date, I just wonder whether Postgres beta
and release candidate cycles are more typically measured in weeks or in
months.
--
Thank you,
Lewis Kapell
Com
something we should be alarmed about, or could this be the
normal result of dumping and reloading a large database?
Thanks for any who can advise.
--
Thank you,
Lewis Kapell
Computer Operations
Seton Home Study School
---(end of broadcast)---
TIP
Sorry, I should have given the versions. The old server was running
8.0.8, the new server is running 8.2.1.
Thank you,
Lewis Kapell
Computer Operations
Seton Home Study School
Tom Lane wrote:
Lewis Kapell <[EMAIL PROTECTED]> writes:
We recently migrated to a new server after having h
erver.
The server is working normally, as far as I can tell, apart from this.
I would be most grateful if anyone can suggest the next step for
troubleshooting this issue.
Thank you.
Lewis Kapell
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscri
l.org
[mailto:pgsql-admin-ow...@postgresql.org] On Behalf Of Lewis Kapell
Sent: Friday, June 05, 2009 10:44 AM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] Postgres has stopped logging
This is a really strange one. We are running PostgreSQL 8.3.7 on a
Fedora Core 8 system (uname -a gives: 2.6.23.1-4
og
2009-06-04 15:46 postgresql-2009-06-04.log
Thank you,
Lewis Kapell
Computer Operations
Seton Home Study School
---
For a free subscription to the Seton Home Study School monthly
electronic newsletter, send an e-mail t
?Ss 0:10 postgres: autovacuum launcher process
2264 ?Ss 4:51 postgres: stats collector process
thanks
Lewis Kapell
Tom Lane wrote:
Lewis Kapell writes:
2) The relevant section of the config file looks like this:
#log_destination = 'stderr'
logging_collec
.
So my problem is solved, although I wish I had some idea what had caused
it in the first place.
Tom Lane wrote:
Lewis Kapell writes:
If I search the output of ps -ax for entries containing both "postgres:"
and "process" I get the following:
2259 ?Ss 0
ocess to obtain a new file handle, or something along those lines.
Thank you,
Lewis Kapell
Computer Operations
Seton Home Study School
---
For a free subscription to the Seton Home Study School monthly
electronic newsletter, send an e-ma
Grittner wrote:
Lewis Kapell wrote:
And anyway, there have now been three additional messages written to
the log file since it was first created.
As long as it continues to log after you start PostgreSQL with the
file already in existence, I guess that's not it. You did try a stop
and
trial and error. I've not had the time
to really brush up on that level of tuning.
If you were planning to upgrade to 8.4 in the near future, then you
wouldn't have to worry about these settings any more. Those settings
tune themselves and they are no longer specified in the configu
The documentation for 8.3 states:
ALTER USER is now an alias for ALTER ROLE.
Under the entry for ALTER ROLE it says:
Caution must be exercised when specifying an unencrypted password with
this command. The password will be transmitted to the server in
cleartext, and it might also be logged i
ointed out, there is a difference between work_mem and
maintenance_work_mem.
Thank you,
Lewis Kapell
Computer Operations
Seton Home Study School
---
For a free subscription to the Seton Home Study School monthly
electronic newsletter, send an
hat's just Postgres' way of showing you what
the data type of the column is.
Thank you,
Lewis Kapell
Computer Operations
Seton Home Study School
---
For a free subscription to the Seton Home Study School monthly
electronic newsletter,
also.
If your database has a lot of tables/indexes such that it would take you
too long to inspect each one, then I don't know what you could do.
Maybe some of the more experienced folks on the list could suggest
something.
Lewis Kapell
Computer Operations
Seton Home Study School
Marc
Eric,
Is the table in question so large that you can't afford the time it
would take to perform ALTER COLUMN TYPE?
I definitely would not go poking around in system catalogs and changing
things there. Not unless you *want* to trash your database... The fact
that 'todo' has not yet been imp
You need to put double-quotes (") around your username, db name etc. -
otherwise everything is reduced to lower case.
Lewis
don...@caltech.edu wrote:
Hi,
I have a trouble in creating user and database in postgres. whenever I
create user or databases in capital letters, the names are always
c
Please see these earlier threads:
Is IDLE session really idle?
http://archives.postgresql.org/pgsql-admin/2009-06/msg00096.php
Idle connections
http://archives.postgresql.org/pgsql-admin/2009-10/msg00017.php
Lewis Kapell
Vladimir Rusinov wrote:
Hi!
We are having a lot of ' in transa
lly uses a backslash to escape a double-quote, but I don't know how
this would affect the bytea values which I discussed above. How are
backslashes affected if they are actually part of the raw data?
--
Thank you,
Lewis Kapell
Computer Operations
Seton Home Study School
--
Sent
address all the concerns which you raised?
Thanks
Lewis
Kevin Grittner wrote:
Lewis Kapell wrote:
I have updated much of our code to use the E'' syntax in order to
suppress these messages.
If you do that, you'd better be doing something to make sure you
have cured the probl
x27;t thought of it until just now, and I would need to test again to
make sure.
Sorry I didn't think this through more carefully before I wrote.
Thanks
Lewis
Kevin Grittner wrote:
Lewis Kapell wrote:
I forgot to mention that all of these insertions are being done
via PHP scripts, and we
Did you issue the reload command using pg_ctl after editing your
postgresql.conf, to tell the server to pick up the changes?
If you issue the following within a psql session, it will tell you what
config value the server is currently using:
show log_line_prefix;
Looks like either you
understand what that '256 bytes' refers to. That is a far cry
from 2kb. I would be grateful if anyone can fill in the evident gap in
my knowledge here.
--
Thank you,
Lewis Kapell
Computer Operations
Seton Home Study School
--
Sent via pgsql-admin mailing list (pgsql-admin@postgr
g database cluster without having to run
initdb again?
On 4/13/2010 3:02 PM, Kevin Grittner wrote:
Lewis Kapell wrote:
I don't understand what that '256 bytes' refers to. That is a far
cry from 2kb. I would be grateful if anyone can fill in the
evident gap in my knowledge
this is what it refers to. Could the WAL/PITR method then be
used to upgrade from 8.3 to 8.4 on the same server and avoid having the
significant downtime of dump/restore?
If so, I understand the two servers would have to run on different
ports. Are there any other issues/traps to be aware of
three hours of down time, but I would
like to avoid it.
Thank you,
Lewis Kapell
Computer Operations
Seton Home Study School
On 4/14/2010 4:28 PM, Iñigo Martinez Lasala wrote:
How big is your database?
If not very big, a pg_dump/pg_restore will be your best option. 8.3 to
8.4 is not a trau
On 4/14/2010 5:11 PM, Greg Sabino Mullane wrote:
If it wouldn't kill you, I'd suck up the time. All other solutions
are going to take additional expertise, prep, and testing.
Keep in mind that if you have tables and/or databases that don't
change frequently, you can dump those beforehand to min
a
different way to build your query that avoids this handicap. Maybe a
new index on your table would help too, perhaps a partial index; but
again, this is just guessing without knowing the nature of your data.
Thank you,
Lewis Kapell
Computer Operations
Seton Home Study School
On 4/13/2010 8:5
.
Also, is it possible you are running out of disk space? Have there been
any other errors recently? Check your operating system logs.
Thank you,
Lewis Kapell
Computer Operations
Seton Home Study School
On 4/19/2010 3:17 AM, Khangelani Gama wrote:
Please assist, I am getting the follo
pg_cancel_backend() and pg_terminate_backend() do different things.
From the documentation:
pg_cancel_backend(pid int) Cancel a backend's current query
pg_terminate_backend(pid int) Terminate a backend
On 4/19/2010 11:07 PM, Scott Marlowe wrote:
On Mon, Apr 19, 2010 at 8:10 PM, Tom La
You misunderstand the purpose of ANALYZE. Postgres needs the results in
order to perform queries efficiently. Whether you have the ability to
change or tune the queries is beside the point.
- Lewis
On 5/14/2010 11:01 AM, Narasimha Murthy-VRFX87 wrote:
Hi Kevin,
Thanks again for a quick re
arasimha Murthy
Cell +91 95814 98895, +91-94940 62794 | 040-2347 2025 (O) | x2025 (O)
-Original Message-
From: pgsql-admin-ow...@postgresql.org
[mailto:pgsql-admin-ow...@postgresql.org] On Behalf Of Lewis Kapell
Sent: Friday, May 14, 2010 8:34 PM
To: pgsql-admin@postgresql.org
Subject: Re: [
32 matches
Mail list logo
