On Monday 23 June 2008 15:45:22 Kynn Jones wrote:
On Mon, Jun 23, 2008 at 2:21 PM, Steve Atkins [EMAIL PROTECTED] wrote:
In real use you're unlikely to hit any limits, theoretical or practical,
but if you start to use a silly number of tables and so on you're likely
to hit performance
Tom Lane wrote:
Rodrigo Gonzalez [EMAIL PROTECTED] writes:
Dont know exactly what you mean, if you are talking about the moment
that I receive the error...
No, it's clear that things are already broken before pg_dump started.
You need to show us how to get to this state from a fresh
Hi everybody.
I have created a table containing an array of points
(each point exists only once in the array).
CREATE TABLE lala (id INT NOT NULL, occur point[] not NULL, PRIMARY
KEY(id));
I am trying to find a way to get the position of array elements
that have a specific x coordinate.
Tom Lane wrote:
Well, both the trigger call API and the underlying implementation deal
in CTIDs, so just airily saying we don't need 'em doesn't obviously
work. (Note I did not say obviously doesn't work. Whether this is
feasible depends on much closer analysis than any of the hand-waving
Hi,
I have recently started experimenting with tsearch2 and it seems that
the default behaviour is to ignore HTML tags and treat them as
word-separators. What I would like it to do is to ignore HTML tags
within words, but instead of creating separate words, combine the
characters
On Thu, 26 Jun 2008, Joanna Sharman wrote:
Hi,
I have recently started experimenting with tsearch2 and it seems that the
default behaviour is to ignore HTML tags and treat them as word-separators.
What I would like it to do is to ignore HTML tags within words, but instead
of creating
On Wed, Jun 25, 2008 at 10:55 PM, Scott Marlowe [EMAIL PROTECTED]
wrote:
Until you benchmark it for your app you really don't know how
inefficient it really is compared to pessimistic locking.
Sure. The question was about more about finding the right approach/layer
for implementing
On Wed, Jun 25, 2008 at 10:21 PM, Craig Ringer [EMAIL PROTECTED]
wrote:
You might want to look into advisory locking. If your locks don't need
to be longer than the life of an active EntityManager session then you
can probably just issue a native query through the EntityManager to
acquire
On Tue, Jun 24, 2008 at 09:16:37AM +0200, Albe Laurenz wrote:
Garry Saddington wrote:
ProgrammingError Error Value: ERROR: character 0xe28099 of
encoding UTF8 has no equivalent in LATIN1 select distinct
[...]
This is UNICODE 0x2019, a right single quotation mark.
This is a Windows
Hi.
I run a function
CREATE OR REPLACE FUNCTION addRating(tbl_ INTEGER,value_ INTEGER)
RETURNS void AS $$
DECLARE
tablename TEXT;
fieldname TEXT;
BEGIN
tablename:='Rating_'||tbl_;
fieldname:='val';
EXECUTE 'UPDATE '||tablename||' SET
Andrew wrote:
Thanks Alvaro.
Please don't forget to CC the list.
Reading the source for the patch, I can see how that should address the
issue. Though I don't really understand how it is working in Linux but
not on Windows. I assume that Linux OS is passing the UTF-8 character
and
Phillip Mills wrote:
On Wed, Jun 25, 2008 at 10:21 PM, Craig Ringer
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
You might want to look into advisory locking. If your locks don't need
to be longer than the life of an active EntityManager session then you
can probably just
Michael Fuhr wrote:
ProgrammingError Error Value: ERROR: character 0xe28099 of
encoding UTF8 has no equivalent in LATIN1 select distinct
[...]
This is UNICODE 0x2019, a right single quotation mark.
This is a Windows character - the only non-UNICODE codepages I
know that contain
At 10:30 PM 6/24/2008, David Siebert wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Which disto is best for running a Postgres server?
I just installed OpenSuse and downloaded and compiled the latest version
of Postgres. It isn't that big of a hassle but I noticed that almost
none of the
On Thu, Jun 26, 2008 at 03:31:01PM +0200, Albe Laurenz wrote:
Michael Fuhr wrote:
Your input data seems to have a mix of encodings: sometimes you're
getting pound signs in a non-UTF-8 encoding, but if characters like
U+2019 RIGHT SINGLE QUOTATION MARK got into the database when
A B [EMAIL PROTECTED] writes:
CREATE OR REPLACE FUNCTION addRating(tbl_ INTEGER,value_ INTEGER)
RETURNS void AS $$
DECLARE
tablename TEXT;
fieldname TEXT;
BEGIN
tablename:='Rating_'||tbl_;
fieldname:='val';
EXECUTE 'UPDATE '||tablename||' SET
On Thursday 26 June 2008 15:41, Michael Fuhr wrote:
On Thu, Jun 26, 2008 at 03:31:01PM +0200, Albe Laurenz wrote:
Michael Fuhr wrote:
Your input data seems to have a mix of encodings: sometimes you're
getting pound signs in a non-UTF-8 encoding, but if characters like
U+2019 RIGHT
On Thu, Jun 26, 2008 at 5:08 AM, Dean Rasheed [EMAIL PROTECTED] wrote:
The Oracle instead of trigger ducks this issue completely. The
trigger is called once per row in the view that matches the top-level
where clause, and it is entirely up to the author of the trigger
function to work out what
I just upgraded to 8.3.3 and taking advantage of the RETURNING clause
which is really cool. I've found that with Pg.pm $r-resultStatus
returns the integer 2 when the RETURNING clause is used on an
insert.
Of course, without using RETURNING the status is the constant
PGRES_COMMAND_OK.
Is
Hi
I'm copying PostgreSQL discussion group in case the following problem
involves their efforts.
I am running Postgresql 8.3 with Postgis latest version and PGAdmin 1.8.2 on
Windows XP.
I imported a shapefile using conversion and upload and it installed with no
problem.
When I viewed
Mike-
If I understand your question you could use a 'row-trigger'
http://download.oracle.com/docs/cd/B10501_01/server.920/a96524/c18trigs.htm#1907
specificy initial filtering thru 'Trigger Restriction'
consequent specifics of which row to process can be handled in the 'Trigger
Action'
Anyone
MS's web site has a good summary at
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/w2000Msgs/60
93.mspx?mfr=true . Their bottom line: Faulty hardware, a buggy system
service, antivirus software, and a corrupted NTFS volume can all generate this
type of error.
If you haven't
Hallo Bob,
I also use pgDmin on XP with postGIS and imported Shape-Files, but without
problems.
As far as I know pgadmin uses gtk, and there are some google-hits for
searchvalues pgadmin and gtk reporting hardware-crashes on windows and
linux Systems.
Perhaps the same problem?
Ludwig
MS's web
On Thu, Jun 26, 2008 at 5:08 AM, Dean Rasheed wrote:
The Oracle instead of trigger ducks this issue completely. The
trigger is called once per row in the view that matches the top-level
where clause, and it is entirely up to the author of the trigger
function to work out what to update (if
On Jun 26, 2008, at 5:41 AM, Rodrigo Gonzalez wrote:
Tom Lane wrote:
Rodrigo Gonzalez [EMAIL PROTECTED] writes:
Craig Ringer wrote:
What platform are you using?
It's running under CentOS 4.4 using ext3, no RAID or LVM.
Server is quad xeon 64 bits 3 GHz
Ugh, I'd have liked to think
Brandon Metcalf [EMAIL PROTECTED] writes:
I just upgraded to 8.3.3 and taking advantage of the RETURNING clause
which is really cool. I've found that with Pg.pm $r-resultStatus
returns the integer 2 when the RETURNING clause is used on an
insert.
Of course, without using RETURNING the
t == [EMAIL PROTECTED] writes:
t Brandon Metcalf [EMAIL PROTECTED] writes:
t I just upgraded to 8.3.3 and taking advantage of the RETURNING clause
t which is really cool. I've found that with Pg.pm $r-resultStatus
t returns the integer 2 when the RETURNING clause is used on an
t insert.
On Thu, Jun 26, 2008 at 12:11 PM, Dean Rasheed [EMAIL PROTECTED] wrote:
This can almost be implemented in PostgreSQL right now, using a rule of
the form ... do instead select trigger_fn() - except, as you point out, the
caller won't know how many rows were actually updated. As far as the
b == [EMAIL PROTECTED] writes:
b t == [EMAIL PROTECTED] writes:
b t Brandon Metcalf [EMAIL PROTECTED] writes:
b t I just upgraded to 8.3.3 and taking advantage of the RETURNING clause
b t which is really cool. I've found that with Pg.pm $r-resultStatus
b t returns the integer 2 when
Under somewhat unusual circumstances, rows in one of our tables have an
'active' flag with a true value. We check for these relatively often since
they represent cases that need special handling. We've found through
testing that having a partial index on that field works well. What seems
odd to
Hello,
I've got a very strange problem that I'm seeing in one of our PostgreSQL
databases (7.4.19). Specifically, I have a query that only uses the
functional index that it's supposed to use if I cast to text.
Here is a slimmed down version of the table definition:
Column |
On Thu, Jun 26, 2008 at 03:24:41PM -0400, Phillip Mills wrote:
dev=# explain analyze select * from result where active = true;
dev=# explain analyze select * from result where active is true;
This is version 8.2.6. Is there something I'm missing that could make these
queries ever produce
use this
explain analyze select * from result where active = 't';
--- On Thu, 6/26/08, Phillip Mills [EMAIL PROTECTED] wrote:
From: Phillip Mills [EMAIL PROTECTED]
Subject: [GENERAL] Partial Index Too Literal?
To: pgsql-general@postgresql.org
Date: Thursday, June 26, 2008, 7:24 PM
Under
I'm running a very large series of commands - mainly DDL but some DML as
well - in a large transaction. I get the following error, which doesn't
seem to be documented:
ERROR: failed to fetch old tuple for AFTER trigger
: COMMIT
There are no triggers that I'm aware of. I've gotten this error
Lincoln Yeoh wrote:
At 10:30 PM 6/24/2008, David Siebert wrote:
Which disto is best for running a Postgres server?
Just to add one more slightly different philosophy.
For servers I manage, I run the most conservative
and slow changing distros that only update security
releases (Debian
the table o tables have triggers?
try to use COMMIT
--- On Thu, 6/26/08, Robert James [EMAIL PROTECTED] wrote:
From: Robert James [EMAIL PROTECTED]
Subject: [GENERAL] Undocumented Postgres error: failed to fetch old tuple for
AFTER trigger
To: Postgres General pgsql-general@postgresql.org
Date:
Robert James [EMAIL PROTECTED] writes:
ERROR: failed to fetch old tuple for AFTER trigger
I'm running Postgres 8.2.1 on Windows XP.
I seem to remember a bug with this symptom; so your first move ought to
be to update to 8.2.latest. If you can still reproduce it afterwards,
please send a test
Dear All,
1. I have heard of problems arising from compiling PostGreSQL (8.3) on 64-bit
processors. What sort of problems am I likely to encounter and how should I fix
them? We are will run Linux Redhat 5 on a Dell PE2950 III Quad Core Xeon E54
2.33 GHz, and a Dell PE2950 III Quad Core Xeon
1. I have heard of problems arising from compiling PostGreSQL (8.3) on
64-bit
processors. What sort of problems am I likely to encounter and how
should I fix
them? We are will run Linux Redhat 5 on a Dell PE2950 III Quad Core
Xeon E54
2.33 GHz, and a Dell PE2950 III Quad Core Xeon L5335
Hello all,
I'm looking for a solution to query a SQL Server 2000 instance from
PostgreSQL 8.3.3.
I've been trawling the internet for some type of solution with out any luck,
I only found old references to someone talking about implementation of
create database link to postgresql
Does
On Thu, 26 Jun 2008, Benjamin Weaver wrote:
I have heard of problems arising from compiling PostGreSQL (8.3) on
64-bit processors.
From who?
We are will run Linux Redhat 5
If there were any problems compiling and running PostgreSQL on 64-bit
RHEL5, I wouldn't be writing this message
On Thu, Jun 26, 2008 at 7:12 PM, Adam Rich [EMAIL PROTECTED] wrote:
1. I have heard of problems arising from compiling PostGreSQL (8.3) on
64-bit
processors. What sort of problems am I likely to encounter and how
should I fix
them? We are will run Linux Redhat 5 on a Dell PE2950 III Quad
On Thu, 26 Jun 2008, Benjamin Weaver wrote:
Dear All,
1. I have heard of problems arising from compiling PostGreSQL (8.3) on 64-bit
processors. What sort of problems am I likely to encounter and how should I fix
them? We are will run Linux Redhat 5 on a Dell PE2950 III Quad Core Xeon E54
Ryan VanMiddlesworth [EMAIL PROTECTED] writes:
I've got a very strange problem that I'm seeing in one of our PostgreSQL
databases (7.4.19). Specifically, I have a query that only uses the
functional index that it's supposed to use if I cast to text.
Yeah, 7.4 is not very bright about
Greg Smith [EMAIL PROTECTED] writes:
On Thu, 26 Jun 2008, Benjamin Weaver wrote:
I have heard of problems arising from compiling PostGreSQL (8.3) on
64-bit processors.
From who?
Perhaps someone who remembers PG 6.4 or thereabouts?
Certainly any version released in the last couple of years
David Rowley wrote:
Hello all,
I’m looking for a solution to query a SQL Server 2000 instance from
PostgreSQL 8.3.3.
I’ve been trawling the internet for some type of solution with out any
luck, I only found old references to someone talking about
implementation of create database link to
Rodrigo Gonzalez [EMAIL PROTECTED] writes:
Tom Lane wrote:
No, it's clear that things are already broken before pg_dump started.
You need to show us how to get to this state from a fresh database.
Interestinga new problem maybe, or maybe the same one
...
ERROR: relation
Hi,
I have problem with my DB:
snort=# vacuum full;
WARNING: index ip_src_idx contains 1921678 row versions, but table
contains 1921693 row versions
HINT: Rebuild the index with REINDEX.
WARNING: index ip_dst_idx contains 1921668 row versions, but table
contains 1921693 row versions
Ganbold [EMAIL PROTECTED] writes:
I have problem with my DB:
ERROR: could not read block 988 of relation 1663/16384/16472:
Input/output error
How to solve this problem?
First, replace your failed disk; then get out your backups and restore
your system ...
regards,
Title: WINiPMail Mail
Dear PostgresqlHi!
How are things going? I'm tae young in KoreaI'm writing to ask you a favor.Now, we are taking a
migration testing about Oracle to enterprisedb
(I know, It's not Postgresql
issue, but I really want tohelp anyone about this)Then we've got
50 matches
Mail list logo
