o validate data integrity *before* putting it into the database.
If there is a problem with any part of the data, I don't want any of it
in the database.
-Jon
--
-**-*-*---*-*---*-*---*-*-*-*---*-*---*-*-*-*-*---
Jon Lapham Rio de Janeiro, Brasil
Tom Lane wrote:
Jon Lapham <[EMAIL PROTECTED]> writes:
Have I (very possible) missed some official
PostgreSQL instructions?
http://www.postgresql.org/docs/8.3/static/textsearch-migration.html
http://www.postgresql.org/docs/8.3/static/tsearch2.html
I haven't personally tried tha
Joshua D. Drake wrote:
Jon Lapham wrote:
How are we, Joe PostgreSQL users on the street, supposed to know which
instructions to follow? Have I (very possible) missed some official
That would be a question for mediawiki people not PostgreSQL people.
Okay, makes sense. It just seemed to me
ere are others. The one common thread
shared by all the instructions are that they say different things. How
are we, Joe PostgreSQL users on the street, supposed to know which
instructions to follow? Have I (very possible) missed some official
PostgreSQL instructions? How do we go about tri
oblem.
--
-**-*-*---*-*---*-*---*-*-*-*---*-*---*-*-*-*-*---
Jon Lapham <[EMAIL PROTECTED]>Rio de Janeiro, Brasil
Personal: http://www.jandr.org/
***-*--**---***---
---(end of broadcast)---
TIP 3: Have you checked our ex
HEN
NEW.textvector := to_tsvector('default',NEW.old_text);
END IF;
RETURN NEW;
END;
This looks like a problem with tsearch2 to me... can anyone give me a
pointer on where to go from here to debug this? Thanks!
-Jon
--
-**-*-*---*-*---*-*---*-*-*-*---
Tom Lane wrote:
Some time ago, Jon Lapham <[EMAIL PROTECTED]> wrote:
Today I had a power outage which upon reboot seems to have done
something to cause Postgresql to not restart properly. This has
happened to me before:
http://archives.postgresql.org/pgsql-general/2006-09/msg00938.ph
cessor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 44
model name : AMD Athlon(tm) 64 Processor 3200+
FWIW: The kernel says SMP, but it is a single core processor.
--
-**-*-*---*-*---*-*---*-*-*-*---*-*---*-*-*-*-*---
Jon Lapham <[EMAIL
Tom Lane wrote:
Jon Lapham <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
It would seem that maybe your kernel has a different idea of what EIDRM
means than we do. You say this persists across a reboot?
I probably should have asked before doing this... but I just rebooted
and postgresq
p the forensics.
So, on the second boot postgresql starts as it should (the first boot
being when I powered up after the power outage).
--
-**-*-*---*-*---*-*---*-*-*-*---*-*---*-*-*-*-*---
Jon Lapham <[EMAIL PROTECTED]>Rio de Janeiro, Brasil
Personal:
Tom Lane wrote:
Jon Lapham <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
Let's see the output from
sudo ipcs -a
[EMAIL PROTECTED] ~]# ipcs -a
[ no postgres-owned segments... ]
Well, that's dang interesting. Could you run the postmaster under
strace and send the output?
Tom Lane wrote:
Jon Lapham <[EMAIL PROTECTED]> writes:
What can I do to help diagnose what is happening?
Let's see the output from
ps auxww | grep postgres
sudo ipcs -a
[EMAIL PROTECTED] ~]# ps auxww | grep postgres
root 3969 0.0 0.0 60272 688 pts/1R+ 15:47
red memory block with the command "ipcclean", "ipcrm", or
just delete the file "postmaster.pid".
--
-**-*-*---*-*---*-*---*-*-*-----*---*-*---*-*-*-*-*---
Jon Lapham <[EMAIL PROTECTED]>Rio de J
, issue the commands, etc.
--
-**-*-*---*-*---*-*---*-*-*-*---*-*---*-*-----*-*-*---
Jon Lapham <[EMAIL PROTECTED]>Rio de Janeiro, Brasil
Personal: http://www.jandr.org/
***-*--**---***---
Tom Lane wrote:
Jon Lapham <[EMAIL PROTECTED]> writes:
To stress test, I turned off the power while actively processing db
operations, such as: loading data into a database, create a new
database, delete contents of a large table within a transaction.
Anyway, in every case I cou
e FC5 (in this case) VM instance to run
through its shutdown procedure, and takes 15 seconds or so to shutdown.
I am using "power off".
--
-**-*-*---*-*---*-*---*-*-*-*---*-*---*-*-*-*-*---
Jon La
Tom Lane wrote:
Jon Lapham <[EMAIL PROTECTED]> writes:
Is it important for you to know that at the time of the power outage, I
*did* have 2 closed source kernel modules loaded, vmware's and NVidia's.
(This is a development machine, not production...). Could one of
these mo
[EMAIL PROTECTED] ~]$ createdb bar
CREATE DATABASE
So, running "createdb bar" a second time works. This is probably not a
bug, but I thought I'd mention it anyway as it could potentially cause
problems for people running scripts.
--
-**-*-*---*-*---*-*---*-*-*-*---*-*---
Tom Lane wrote:
Adrian Klaver <[EMAIL PROTECTED]> writes:
On Sunday 24 September 2006 09:17 am, Tom Lane wrote:
Jon Lapham <[EMAIL PROTECTED]> writes:
FATAL: pre-existing shared memory block (key 5432001, ID 65536) is
still in use
This is extremely odd, because a shared memory
Tom Lane wrote:
Jon Lapham <[EMAIL PROTECTED]> writes:
I recently had another electrical power outage that left my machine
unable to restart postgresql. I had previously reported this a while ago:
http://archives.postgresql.org/pgsql-general/2005-04/msg01286.php
Anyway, because
postgresql start
Starting postgresql service: [ OK ]
PS: This email is just a FYI, not a complaint. Maybe it is just a right
of passage that users of postgresql will just have to learn about this.
--
-**-*-*---*-*---*-*---*-*-*-*---*-*---*-*-*-*-*---
Jon Lapham <
'm blind, I didn't see this in the docs. :)
-Jon
--
-**-*-*---*-*---*-*---*-*-*-*---*-*---*-*-*-*-*---
Jon Lapham <[EMAIL PROTECTED]>Rio de Janeiro, Brasil
Personal: http://www.jandr.org/
***-*--**---***---
---(end of broadcast)--
bove.
Extra information that may be useful:
test=> select version();
version
-
PostgreSQL 8.1.4 on i386-redhat-linux-gnu, compiled by GCC
i386-re
ars of using PostgreSQL, I did not know
you can "SELECT tablename FROM tablename".
Thanks Michael.
PS: Does anyone know if this very portable to other databases?
-Jon
--
-**-*-*---*-*---*-*---*-*-*-*---*-*---*-----*-*-*-*---
Jon Lapham <[EMAIL PROTECTED]>
thing like this:
select id, md5(*) from mytable;
...which of course does not work.
Thanks for any ideas!
-Jon
--
-**-*-*---*-*---*-*---*-*-*-*---*-*---*-*-*-*-*---
Jon Lapham <[EMAIL PROTECTED]>Rio de Janeiro, Brasil
Personal:
t timeit(100);
Time: 22145.408 ms
But, this is less than a factor of 2 difference, similar to what one of
the previous INSERT examples showed. Or am I missing something?
--
-**-*-*---*-*---*-*---*-*-*-*---*-*---*-*-*-*-----*---
Jon Lapham <[EMAIL PROTECTED]>
Tom Lane wrote:
Jon Lapham <[EMAIL PROTECTED]> writes:
So, then it would be correct to change my init scripts to do the
following: (if so, this patch can be applied to the 7.4 branch)
I would recommend strongly AGAINST that, because what you just did was
remove the defense against starti
Tom Lane wrote:
Jon Lapham <[EMAIL PROTECTED]> writes:
After a power outage (and bad UPS combo, or plug pull, or bad RAM, etc)
sometimes (I would guess <10% of the time) postgresql fails to restart
automatically after booting the computer. Invariably, it is because the
"postma
-q postgresql
postgresql-7.4.7-3.FC3.1
--
-**-*-*---*-*---*-*---*-*-*-*---*-*---*-*-*-*-----*---
Jon Lapham <[EMAIL PROTECTED]>Rio de Janeiro, Brasil
Personal: http://www.jandr.org/
***-*--**---***---
Tom Lane wrote:
Bruno Wolff III <[EMAIL PROTECTED]> writes:
Jon Lapham <[EMAIL PROTECTED]> wrote:
When using queries with aggregate functions, is there any way to not
have to have to explicitly write all the columns names after the GROUP
BY ? I would like to use a wildcard "
any advice on how to handle this,
-Jon
PS: I'm using postgresql v7.4.x
--
-**-*-*---*-*---*-*---*-*-*-*---*-*---*-----*-*-*-*---
Jon Lapham <[EMAIL PROTECTED]>Rio de Janeiro, Brasil
A simple rename command put
everything back together again.
Now I can sleep.
--
-**-*-*---*-*---*-*---*-*-*-*---*-*---*-*-*-*-*---
Jon Lapham
Extracta Moléculas Naturais, Rio de
32 matches
Mail list logo
