On Wednesday November 8 2006 12:30 pm, Shoaib Mir wrote:
> To be specific you need to look at the syslogs to see if it
> was actually some OOM killer or not.
I checked all db logs + syslog, of course. All they show is the
process receiving SIGKILL (followed by all others being shutdown
as a res
On Wednesday December 21 2005 8:24 pm, Tom Lane wrote:
> "Ed L." <[EMAIL PROTECTED]> writes:
> > I have a cluster configured for ~800MB of shared memory
> > cache (shared_buffers = 10), but ipcs shows TWO shared
> > memory segments of ~800MB belonging to that postmaster.
> > What kind of a pro
On Monday May 22 2006 4:43 pm, Tom Lane wrote:
> "Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> > On Wed, May 17, 2006 at 10:29:14PM -0400, Tom Lane wrote:
> >> The reason the default is currently 10 is just
> >> conservatism: it was already an order of magnitude better
> >> than what it replaced (a
Peter Eisentraut wrote:
>
> Ed Loehr writes:
>
> > This query works in 7.0.3...
> >
> > SELECT p.*, e.id AS "employee_id", e.ref_name,
> >e.business_line_id, e.record_status_id AS "emp_record_status_id"
> > >FROM perso
issue?
Regards,
Ed Loehr
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
On Friday October 10 2003 4:46, Ed L. wrote:
> I have libpq client program that repeatedly connects to a DB, queries,
> and then disconnects. After a seemingly random number of such successful
> sessions (sometimes 30, sometimes hundreds), the backend mysteriously
> exits after the client calls PQ
LE will create implicit sequence 'foo_id_seq' for
SERIAL column 'foo.id'
NOTICE: CREATE TABLE/PRIMARY KEY will create implicit index 'foo_pkey'
for table 'foo'
CREATE
testdb=# \d foo
Table "foo"
Attribute | Type | Modifier
---+-+--
id| integer | not null default nextval('foo_id_seq'::text)
Index: foo_pkey
Regards,
Ed Loehr
ting down the database.
Hmmm. My backup procedure, based on earlier discussions in this group,
involves blocking all write-access during a pg_dump. That is effectively
shutting down the database from my perspective. Is there a quicker way
to take a consistent snapshot while still allowing writes?
Regards,
Ed Loehr
Can other folks confirm that this is no longer a problem? Are people
successfully vacuuming while allowing full read/write access to the db?
Regards,
Ed Loehr
there will be some improvements on
the vacuum front in a coming release).
Regards,
Ed Loehr
> At 12:16 PM 5/31/00, Ed Loehr wrote:
> >Bruce Momjian wrote:
> > >
> > > > Alex Pilosov wrote:
> > > > >
> > > > > > http://networkdna.com
ses). Any insight on these two problems would be appreciated
> greatly.
Hello Jerry,
What version are you running?
What does your server log show? Any other logs?
Can you show us the small query, # of rows, etc?
Regards,
Ed Loehr
ollowed by
select avg(age_sum/count) from temp_age;
Regards,
Ed Loehr
Tom Lane wrote:
>
> Ed Loehr <[EMAIL PROTECTED]> writes:
> >> Then, start this one in another bash window/terminal/whatever...
> >>
> >> % while test 1; do echo -n "`date`: "; psql -d pdb -c "vacuum analyze;
> >> select count(*)
Tom Lane wrote:
>
> Ed Loehr <[EMAIL PROTECTED]> writes:
> >>>>> % while test 1; do echo -n "`date`: "; psql -d pdb -c "vacuum analyze;
> >>>>> select count(*) from foo;"; sleep 3; done
> >>>>>
> >>
Can anyone point me to any online documentation on how to use the
'BETWEEN' operator/function? (As in "SELECT * FROM foo WHERE id BETWEEN
...")
Regards,
Ed Loehr
7;t understand very well how
these are used. Maybe someone else can say or you can experiment...
Regards,
Ed Loehr
(PS: Posting to only one of -general or -sql will almost always be
sufficient.)
ns in the table, so I can duplicate my code without
> changing too much. Is there anything available to do this? I've yet to find
> it in the documentation, though I may have simply missed it, as I'm new to
> PostgreSQL... Any help is appreciated...
I believe DBI/DBD does this for you:
while ($row_href = $sth->fetchrow_hashref)
{
push( @taghash, $row_href);
}
Regards,
Ed Loehr
Matt Housh wrote:
>
> Does PostgreSQL support something like mySQL's auto_increment tag?
See question 4.16.1 of
http://www.postgresql.org/docs/faq-english.html
Regards,
Ed Loehr
les and 50 foreign keys).
Regards,
Ed Loehr
Can anyone tell me how to log the db user name and db name to the server
log? Is this possible at present? Couldn't find anything about it in
the docs or deja...
Regards,
Ed Loehr
Given UNIONs are not implemented within views in 7.0.3, what are the
generally suggested work-arounds, if any?
Regards,
Ed Loehr
from applications
that may need to access your db. That frees you to change the internal
schema somewhat as long as you honor the agreed "interface" of the
view...
Regards,
Ed Loehr
ate/reload the table?
I'm looking for something like "ALTER TABLE foo ALTER COLUMN id DROP NOT
NULL", but the docs don't hint at it...
Regards,
Ed Loehr
Tom Lane wrote:
>
> Ed Loehr <[EMAIL PROTECTED]> writes:
> > I need to alter the table to get rid of the "NOT NULL" constraint on the
> > 'id' column. Can I do this using ALTER TABLE?
>
> There isn't an ALTER TABLE variant for this at the
Gregory Wood wrote:
>
> What would be nice is if there were a way to only DROP a table if it exists.
> But I would consider this to be rather low priority.
This might help...
CREATE FUNCTION table_exists(TEXT) RETURNS BOOLEAN AS
'DECLARE
tablename ALIAS FOR $1;
temp RECORD;
BEGI
my
example).
http://www.postgresql.org/docs/postgres/x1137.htm :
"'now' is resolved when the value is inserted, 'current' is
resolved everytime the value is retrieved."
Any clues?
Regards,
Ed Loehr
BTW, here's the sequence I used to conclud
10: NOTICE: identifier
"process_state_subscription_id_seq" will be truncated to
"process_state_subscription_id_s"
psql:/home/ed/pgbug:10: ERROR: Relation
'process_state_subscription_id_s' does not exist
Regards,
Ed Loehr
begin:vcard
n:Loehr;Ed
tel;cell:512 751 7734
tel;fax:
Tom Lane wrote:
>
> Ed Loehr <[EMAIL PROTECTED]> writes:
> > Maybe someone can confirm what looks like a long-name-truncation bug in
> > 7.0.0?
>
> I see no bug here; it told you what name it planned to use for the
> sequence:
>
> > psql:/home/ed/
I wanted to use PL/pgsql to write functions for use with
triggers, and thought others might benefit from a concise description
of how to enable this without having to scour the postgresql
documentation. This was with a default install of pgsql v6.5.2 on
RH6.0.
CREATE FUNCTION plpgsql_call_h
> Date: Wed, 17 Nov 1999 20:53:33 +0100
> From: Herbert Liechti <[EMAIL PROTECTED]>
> Subject: sql question
>
> I have a sql problem which I can't solve. The following table is defined
>
> create table AdressGroup
> (
>AdrGroup_Id INTEGER NOT NULL
> DEFAULT N
Bill Sneed wrote:
> I'd like to be able to find a book title that contain C++ in the
> title
>
> select * from books where title ~* 'C++' doesn't work.
>
> I've tried all the basic methods of quoting the Plus (+) signs but
> none seem to work...
>
> Any hints would be most appreciated
>
Bruce Momjian wrote:
> > Peter Eisentraut wrote:
> >
> > > This is getting to be our favourite error message...
> > >
> > > It is caused by a corrupted B-Tree index. Drop and recreate that one.
> >
> > Thanks. Unfortunately, the lack of context to the error message makes it difficult
> > to iden
latter explanation seems more plausible, as I do not have any
columns approaching 512 bytes, much less 4K. Glad to hear it may be coming from an
error
rather than normal usage, though it'd be nice to optionally have corrupted indices
automatically rebuilt.
Cheers.
Ed
Ed Loehr wrote:
> Bruce
quences already provide this
> functionality, surviving dump/reloads
The postgres SERIAL type, which is a sequence, is fairly well-suited to
primary key usage. See PG documentation for details...
Cheers.
Ed Loehr
e when setting up procmail to
spend some time carefully reviewing the various procmail filter options
(on the man page) that follow the colon. They allow you to chain
filters together and control the flow and exit point of mail through
your filter chains.
Cheers.
Ed Loehr
Mark Dalphin wrote:
> Sometimes, however, rather than using the "\i" command, I would like to simply
> load my schema directly into psql and capture the output on STDOUT (ie "psql <
> mySchema.sql >& myOutput"). The problem that arises is that the errors and
> notices all come out on STDERR. I
Kevin Heflin wrote:
> I've been looking through the online docs, so far have not found this
> information.
>
> After an INSERT, I want to retrieve the value of the sequence I use for
> unique_ids
>
> Any suggestions ?
Use the OID returned from the INSERT to select the newly created value,
i.e.,
"Ross J. Reedstrom" wrote:
> Gah, this is getting a bit annoying, correcting this bit of
> mis-information.
>
> currval() is kept as part of the session context, as is completely
> multi-user safe. That's why the person you quoted said 'in the same
> session'.
>
> Where is everyone coming up with
vacuuming
is needed, and would like to hear any advice on how folks are successfully
doing this or think would best be done.
Any comments?
[Hackers: it'd be nice to have pgsql optionally take care of this...]
I'm using Pg 6.5.2 on RH Linux 6.0 2.2.5-15smp via perl DBI/DBD::Pg...
Thanks in advance,
Ed Loehr
Question: is it safe to insert/update/delete during VACUUM?
Ed
Syntax:
postmaster -p
Examples:
postmaster -p 5432
postmaster -p 5433
Cheers,
Ed
Robert Wagner wrote:
> I'm attempting to run two different postmasters on two different HP-UX
> servers, servicing two different apps. The only commonality is that I'm on
> one terminal.
>
> The firs
ng up pgsql/apache on such a system with software raid (no
clear showstopping problems yet).
Thanks,
Ed Loehr
.
Latest incantation of pg_options is:
verbose=2
query
Also tried...
all
verbose=2
query
Cheers,
Ed Loehr
"Culberson, Philip" wrote:
> Oh, one more thing. I've always made the edit BEFORE running ./configure.
>
> Phil Culberson
>
> --
ow working. Thanks
much for your efforts.
Cheers,
Ed Loehr
"Culberson, Philip" wrote:
> Ed,
>
> Configure will used cached values if config.cache is available so you may
> consider first doing a "make distclean", which is the mother of all
> cleanouts. Then
I've seen this a few times. It usually results from an unescaped
embedded apostrophe, e.g.,
INSERT INTO ybsc_note (rem) VALUES ('This don't work 'cuz there ain't no
escapes or backslashes around my single quotes.');
Cheers,
Ed Loehr
pawel wrote:
> Hi,
>
See
http://www.PostgreSQL.ORG/mhonarc/pgsql-general/
Cheers.
Anyone seen this message or know what it means?
NOTICE: Index pg_proc_prosrc_index: NUMBER OF INDEX' TUPLES (1071) IS
NOT THE SAME AS HEAP' (1070)
Cheers,
Ed Loehr
Bruce Momjian wrote:
> > Anyone seen this message or know what it means?
> >
> > NOTICE: Index pg_proc_prosrc_index: NUMBER OF INDEX' TUPLES (1071) IS
> > NOT THE SAME AS HEAP' (1070)
>
> Drop index and recreate. Next release will be more specific in error
> message.
I have no idea *which* ind
ffending index will be auto-corrected on the fly? That
would be almost as good as preventing the root cause in the first place...
Cheers,
Ed Loehr
In 7.1, I think this problem will
> go away, if not in 7.0.
Is the problem well-understood? Is there a place where I can read up on it? This
kind of instability is painful enough to get me thinking about trying to hack my
distribution...
Cheers,
Ed Loehr
rata. But maybe my assumptions are
incorrect or I didn't understand what you mean by harmless?
Cheers,
Ed Loehr
e other people can chime in here. Why are you getting the inital
> crashes?
I don't know. My only suspect right now is that it may be the residual effects of
having
parameter mismatches in 'RAISE' statements in PL/pgSQL. In any event, I'll try to
collect
some data for troubleshooting...
Cheers,
Ed Loehr
Peter Berghold wrote:
> Hi Folks,
> Does anyone out there know of a DBI driver for Postgres for Perl? I
> searched CPAN and didn't see one. Maybe I'm looking in the wrong
> spot...
It's there...DBD::Pg, by E. Mergl. Works well.
Cheers,
Ed Loehr
mission-critical 24x7
applications. And if the masses leave because of system reliability problems, you
can be very, very certain about what they will tell their friends and coworkers.
Cheers,
Ed Loehr
See DBD-Pg under http://www.cpan.org/modules/by-module/DBD/
Ed Loehr wrote:
> Peter Berghold wrote:
>
> > Hi Folks,
> > Does anyone out there know of a DBI driver for Postgres for Perl? I
> > searched CPAN and didn't see one. Maybe I'm looking in the wrong
&g
about what they will tell their friends and coworkers.
>
> And we don't have a problem in this area, do we?
Please tell me you're kidding.
Cheers,
Ed Loehr
rective action if by chance current assumptions are wrong.
Cheers,
Ed Loehr
"Marc G. Fournier" wrote:
> On Sun, 26 Dec 1999, Ed Loehr wrote:
>
> > Bruce Momjian wrote:
> >
> > > We don't have roll-forward logging until 7.1, and require vacuum
> > > regularly. Other than that, I don't know of any major issues.
>
Stephen Birch wrote:
> I am not having any luck searching the archives, is the software down?
>
> http://www.PostgreSQL.ORG/mhonarc/pgsql-general/
>
> Steve
Usually down lately. Try www.deja.com...they have all the posts...
Cheers,
Ed Loehr
rc/test/regress/sql/plpgsql
Cheers,
Ed Loehr
Bruno Mendonca wrote:
> Good evening, where I find information
> about postgres functions.The command \df d'ont show me anything
www.postgresql.org under "Info Central"...
Cheers,
Ed Loehr
/sent
! 0/0 [0/0] voluntary/involuntary context switches
I started postmaster with the following command: postmaster -i
-o "-F -S 4096 -s"
And I have no pg_options file at all.
Cheers,
Ed Loehr
pgsql yielded no results moments ago.
Cheers,
Ed Loehr
Ed Loehr wrote:
> The Hermit Hacker wrote:
>
> > Well, we've finally gotten what seems to be a working version of this
> > going, and, so far, I'm quite impressed...
> >
> > If you go to http://www.postgresql.org/cgi/search.cgi (URL to change), you
> &
I said: "There aren't any results for pgsql..."
The Hermit Hacker wrote:
> ... and the database is just being populated right now, and ...
D'oh!!! Read more carefully! My apologies for the brain-dead spam...
Robert Rothe wrote:
> When I type the following at the psql prompt:
>
> select timestamp('now');
Try
select timestamp(now());
Cheers,
Ed Loehr
function...
Cheers,
Ed Loehr
Oh, and one other thing...
The example has a typo. In the function, 'temp' and 'cust' should be the
same variable (doesn't matter what it's called).
Cheers,
Ed Loehr
Ed Loehr wrote:
> Sarah Officer wrote:
>
> > Can anyone set me straight here? An
I'd like to grant read-access to every single DB object in a database
for one user. I'd hoped for
GRANT SELECT ON * TO
but the '*' syntax is wrong and I don't see an alternative in the
docs...
How is this done?
Cheers,
Ed Loehr
our query gets
translated into... a very annoying bug, indeed. This is the number one
barrier to my ODBC use as it makes views pretty much unusable.
Cheers,
Ed Loehr
shows up when you have
dropped and recreated the function, thinking that the trigger would be
able to find your new function, when in fact it cannot. If you
drop/recreate the function, you must then also drop/recreate the
trigger. Bummer, but I believe that is going to be fixed sometime
soon IIRC.
Cheers,
Ed Loehr
dropped and recreated. Otherwise postgres
> 6.5.3 will give a runtime error that the cache lookup failed.
More generally, any function that gets dropped/recreated requires all
the functions/triggers above it in the call chain to be recreated,
IIRC.
Cheers,
Ed Loehr
Not certain, but I think you get an error message like that when you
rollback at inappropriate (but harmless?) times, as in when you are
not in a transaction or have nothing pending on the current
transaction.
Cheers,
Ed Loehr
> Graeme Merrall wrote:
>
> Hi.
> I've been gett
Correction: this message happens when you 'commit' but without
anything to commit.
% destroydb test; createdb test; psql -d test -c "commit"
NOTICE: EndTransactionBlock and not inprogress/abort state
END
Cheers,
Ed Loehr
Graeme Merrall wrote:
>
> > Not certain,
Ed Loehr wrote:
>
> Correction: this message happens when you 'commit' but without
> anything to commit.
>
> % destroydb test; createdb test; psql -d test -c "commit"
> NOTICE: EndTransactionBlock and not inprogress/abort state
> END
And it seems to b
58392
I suspect vacuum also would have a dramatic impact on performance in
your test case.
Cheers,
Ed Loehr
? I was expecting to have to recompile the
kernel, but would be oh-so-pleased if it were that easy.
Thanks in advance...
Cheers,
Ed Loehr
, but rather how much
*activity* (ie., inserts/deletes) has occurred since you last
vacuumed...
Cheers,
Ed Loehr
karounds.
Other tools: mailing list archive search engine via
(http://www.postgresql.org/lists/mailing-list.html) ... availability
seems to be spotty, though this search engine is just recently
redesigned...
Cheers,
Ed Loehr
> Thoughts or help?
A very frequent problem, many reports in the list archive...Broken (or
shall I say unusable) since March, 1998, if I read the archives
correctly...IIRC, rumored to be fixed in v7.0 sometime in the coming
months...Until then, answer seems to be to make smaller views.
Bummer, yes.
Cheers,
Ed Loehr
hive on how to retrieve a new value for
the purpose of a foreign key (keywords: SERIAL, nextval, sequence).
http://www.postgresql.org/docs/postgres/datatype.htm#AEN842
Cheers,
Ed Loehr
ng against the problem scenarios at the application
level. I confess ignorance on refint.*...
Cheers,
Ed Loehr
" servers keep their own (partial?)
database and manage the transaction issue with a "local" sequence
object. It would have to make sure to constrain the domain of the
local sequence object to that range which was allocated from the
central seed server. I suppose one might need the central seed server
to be using a sequence object as well.
Cheers,
Ed Loehr
[EMAIL PROTECTED] wrote:
>
> On Mon, 7 Feb 2000, Ed Loehr wrote:
>
> > These are resolvable problems. One way to do a programmatic ID
> > generation as David B. suggests is to have a DB server whose purpose
> > is to issue "seed numbers" which designate
Michael Poon wrote:
>
> How can we do STORED PRECEDURE in PostgreSQL?
Several options exist (C, SQL, PL/pgSQL...). For starters, see CREATE
FUNCTION at
http://www.postgresql.org/docs/postgres/index.html
Cheers,
Ed Loehr
G 6.5.3
IIRC, this is a known issue with 'IN', and that the traditional
solution was to replace use of 'IN' with 'EXISTS', i.e.,
and EXISTS (select * from userdir where user_name = username and
towncode...)
Cheers,
Ed Loehr
3) that finds all
appointments for a person?
Cheers,
Ed Loehr
> >> I was previously thinking that I needed to do something like creating the
> >> following table:
> >>
> >> 3) date | doctor | 0800 | 0815 | 0830 | 0845 | 0900 and so on every
> 15
> &g
| TIMESTAMP []
> [ WITH TIME ZONE ]
>
> So the three SQL92 datetime types are DATE, TIME, and TIMESTAMP.
Hi Ross,
Is the standard document you referenced online?
Cheers,
Ed Loehr
can I find it.
Here are a few pl/pgsql references I've found helpful:
Enabling PL/pgSQL: http://www.deja.com/getdoc.xp?AN=548176178
The "manual", AFAIK:
http://www.postgresql.org/docs/postgres/xplang19388.html
Examples: .../postgresql-6.5.*/src/test/regress/sql/plpgsql.sql
Cheers,
Ed Loehr
Ed Loehr wrote:
>
> Timothy Grant wrote:
> >
> > Hi,
> >
> > I keep seeing references to server side scripting and something called
> > PL/SQL, I found some mention of extending it in the programmers
> > reference, but I am unable to find any reference m
ndex scan query will
> be missing a row.
Hmmm. Here's a bit more history for the puzzle and maybe another
possible remedy/workaround/cleanup...
http://www.deja.com/getdoc.xp?AN=471547594
http://www.deja.com/getdoc.xp?AN=575819776
Regards,
Ed Loehr
informative (and most time consuming) answer to
your question is probably to get the beta and hammer on it. But you
might find a few known issues by searching the hackers list via
deja.com or the pgsql web site search engine. There has been some
discussion there, though I haven't kept up. Search for stuff by Jan
Wieck (FKeys leader).
Cheers,
Ed Loehr
kend server
crashes. Your server logs will usually reveal the problem. If you
don't know anything about server logs, checkout the installation guide
section under "starting postgres" or some such section...
Cheers,
Ed Loehr
nswered...
I believe it means that the indices "error_interface_idx" and
error_ewhen_idx" have become corrupted. The fix is to drop and
rebuild them.
Cheers,
Ed Loehr
oreign key in myItem, i.e.,
Table ACL:
uniqid integer not null unique, -- or use pgsql 'serial' type...
...
Table myItem:
uniqid integer not null unique,
...
ACL_uniqid integer not null -- a foreign key into ACL
Cheers,
Ed Loehr
Ed Loehr wrote:
>
> Jason Vasquez wrote:
> > Basically, I'd like to set up an ACL-like property for each record. A table
> > could be strucured like this:
> >
> > Table ACL:
> >Attr
hat. In that case it
> will be *hard*.
Forgive me if I already said this...May I suggest a lovely little perl
package called Statistics::Descriptive which I use for this sort of
thing? I know it's not exactly what your were looking for, but it's a
possible consideration if you happen to be accessing pgsql via
perl/DBI.
Cheers,
Ed Loehr
Chris Carbaugh wrote:
>
> Havn't got any responses yet though. Has anybody installed under RH6.1?
I have installed successfully under rh6.1. What's seems to be wrong?
> Raigo Lukk wrote:
> >
> > What is the way of creating Exceptions in PostgreSQL 6.5.3?
The pl/pgsql wording is
RAISE EXCEPTION ''Something exceptional happened...''.
See http://www.postgresql.org/docs/postgres/xplang19397.htm
Raigo Lukk wrote:
>
> What is the way of creating Exceptions in PostgreSQL 6.5.3?
http://www.deja.com/getdoc.xp?AN=570616874
1 - 100 of 125 matches
Mail list logo
