On Mon, Jan 29, 2007 at 03:46:34PM -0500, Pierre Thibaudeau wrote:
> * Windows XP does support UTF8, yet it is not possible (as far as I
> know) to define one's locale to have anything to do with UTF8
> (presumably in the sense that UTF8 isn't an aspect of a specific
> locale): there is no en_US.U
There is such timeout from the database server for the idle connections but
yes you can always use firewall settings in order to do that and kill idle
connections.
--
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)
On 2/6/07, Gurjeet Singh <[EMAIL PROTECTED]> wrote:
On 1/30/07, Alvaro Herrera <
This error actually indicates that the host and port information you are
providing for the PostgreSQL database server is incorrect or there is not
database server running on that (or it might be the firewall settings too).
First of all what I will recommend is to check on your database server to
gf wrote:
Hello all,
I was recently installing pg on a virtual machine. I also had pg installed
and working on my local machine.
On the vm I was having some issues installing a Drupal db so in searching
for a solution I found a recommendation of the following:
net user postgres /delete
and then r
In article <[EMAIL PROTECTED]>,
"Jim C." <[EMAIL PROTECTED]> writes:
> Maybe it is and maybe it isn't. I wouldn't know. I'm merely the
> unfortunate soul chosen to convert this from MySQL to Postgres. :-/
> I've been working on it for a week now. I've got to say that it pains me
> to know that
finecur wrote:
Hi,
Can I list tables and the time they were last update (adding columns,
drop columns) using sql, something like the "ls -l" command under
unix?
No. There's no automatic timestamping. You could add your own triggers
if you wanted though.
Can I compare the table definitions
What is best way to retrieve all affected tables of an select statement?
(Besides parsing the raw SQL).
Thanks.
--
Regards,
Hannes Dorbath
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgr
Hi all,
As I am inserting 100million rows daily into partitioned tables (daily wise),
it is getting slower. Even the retrivel of data, select statement on those
tables takes about 30 mintues. I have tried increasing the parameters in
postgres.conf but still that doesn't help me much as the
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of roopa perumalraja
Sent: Tuesday, February 06, 2007 12:33 PM
To: pgsql-general@postgresql.org
Subject: [GENERAL] Storing database in cluster (Memory)
Hi all,
As I am inserting 100million rows daily into
Hi,
Today suddenly our PostgreSQL 8.1 server started producing strange errors.
Error occurs during simple updates:
"Table has type character varying, but query expects character varying."
We are still trying to figure out the problem. I've googled for this error
but found nothing. Any insight?
Hannes Dorbath wrote:
What is best way to retrieve all affected tables of an select statement?
(Besides parsing the raw SQL).
From where? As a client-application function? As a user-callable
function in the server? From within the parse/execute code?
--
Richard Huxton
Archonet Ltd
-
Hello List-
I'm having some problems in my program that I've been spending the day
going over and over and am now going to ask for some help, as I cannot see
the problem, but am hoping some seasoned sets of eyes will!
I have some VIEWS that need to get updated when the user chooses to delete
d
> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ümit Öztosun
> Sent: Tuesday, February 06, 2007 2:50 PM
> To: pgsql-general@postgresql.org
> Subject: [GENERAL] Very strange error
>
>
> Hi,
>
> Today suddenly our PostgreSQL 8.1 server started produci
roopa perumalraja wrote:
Hi all,
As I am inserting 100million rows daily into partitioned tables
(daily wise), it is getting slower.
What is - the inserts? By how much? What tables? What indexes? How are
you inserting these rows?
> Even the retrivel of data, select
statement on those table
On 06.02.2007 14:19, Richard Huxton wrote:
What is best way to retrieve all affected tables of an select
statement? (Besides parsing the raw SQL).
From where? As a client-application function? As a user-callable
function in the server? From within the parse/execute code?
From a client appli
Hannes Dorbath wrote:
On 06.02.2007 14:19, Richard Huxton wrote:
What is best way to retrieve all affected tables of an select
statement? (Besides parsing the raw SQL).
From where? As a client-application function? As a user-callable
function in the server? From within the parse/execute code
Borland simply chose a modified MPL to release their InterBase 6 under.
They have since release InterBase 6 under a commercial license, and have
also released InterBase 7 under a commercial license. MPL is a fairly
common license. Sun's CDDL is a modified MPL, for example. The MPL is
somewhere b
This is one instance where I think PGAdmin would really help. You know
what the schema needs to be, yes? Create it will PGAdmin and you can
see what some well-formatted PG code looks like.
The majority of the differences in syntax between MySQL and PG are
*generally* MySQL's fault. MySQL has mo
Have you installed any updates for PostgreSQL? The latest security update
fixed something with type checks or so.
I've seen the same error message also on the BUGS mailing list concerning
a
broken CHECK constraint on a table row.
Perhaps this is the cause of the error messages.
Well, I've just
When does this error crop up? What is the query? Does this select
involve more than one table, or does it involve any homemade
functions? Or overriden functions?
On Feb 6, 2007, at 9:58 AM, Ümit Öztosun wrote:
Have you installed any updates for PostgreSQL? The latest security
update
On 06.02.2007 15:00, Richard Huxton wrote:
Hannes Dorbath wrote:
On 06.02.2007 14:19, Richard Huxton wrote:
What is best way to retrieve all affected tables of an select
statement? (Besides parsing the raw SQL).
From where? As a client-application function? As a user-callable
function in th
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ümit Öztosun
Sent: Tuesday, February 06, 2007 3:59 PM
To: [EMAIL PROTECTED]
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Very strange error
Have you installed any updates for PostgreSQL? The
I wanted to play with ltree, but I'm having trouble running ltree.sql.
Everything in ltree.sql seems to work, except for the CREATE OPERATOR
CLASS statements, which error out like:
ERROR: syntax error at or near "OPERATOR10"
LINE 3: OPERATOR10<@ (_ltree, ltree)RECHECK ,
...which is generated fro
Hello there!
I suggest to post this on the BUGS mailing list. As said before, there has
been some other mail with exact the same error message and with the latest
version something concerning data type checks had been fixed.
Greetings,
Matthias
I'm writing a seperate e-mail to the pgsql-bu
I'm working on a system where postgres 8.2.1 was built from source on
Solaris 10 using gcc. Based on a number of recommendations, we
decided to rebuild postgres Sun Studio cc. Without changing
platforms, I wouldn't've expected the compiler to make a difference,
but we just built 8.2.2 from
Ron Peterson <[EMAIL PROTECTED]> writes:
> I wanted to play with ltree, but I'm having trouble running ltree.sql.
> Everything in ltree.sql seems to work, except for the CREATE OPERATOR
> CLASS statements, which error out like:
> ERROR: syntax error at or near "OPERATOR10"
> LINE 3: OPERATOR10<@
Richard Huxton wrote:
Hannes Dorbath wrote:
http://pgfoundry.org/projects/pgmemcache/
We'd like to use pgmemcache with PG 8.2. The memcached version
doesn't matter much (1.2.x is current, 1.1.x would be fine as well).
It fails to build against 8.2 with various errors. The project seems
unma
On Tue, Feb 06, 2007 at 09:43:01AM -0600, Thomas F. O'Connell wrote:
> DETAIL: Table has type character varying, but query expects
> character varying.
In another thread, someone else is reporting this too. I'm
wondering whether something went wrong in the 8.2.2 release.
A
--
Andrew Sulliva
I need to purchase a new server to put posgresql on that will be acting as the
DBMS server for Apache ofBiz soon. While googling around for performance tweaks
I saw this at http://revsys.com/writings/postgresql-performance.html
CPUs — The more CPUs the better, however if your database does not
Jim C. wrote:
I'm doing this table by table, line by line. Each table, I learn
something new about the differences between MySQL and Postgres, I
mentally catalog it and I can always look it up in my own code next time
for examples.
I've a tool that is providing some help but sometimes it choke
On Tue, Feb 06, 2007 at 09:43:01AM -0600, Thomas F. O'Connell wrote:
> DETAIL: Table has type character varying, but query expects
> character varying.
In another thread, someone else is reporting this too. I'm
wondering whether something went wrong in the 8.2.2 release.
Is this the other thr
On Tue, Feb 06, 2007 at 10:45:23AM -0500, Tom Lane wrote:
> Ron Peterson <[EMAIL PROTECTED]> writes:
> > I wanted to play with ltree, but I'm having trouble running ltree.sql.
> > Everything in ltree.sql seems to work, except for the CREATE OPERATOR
> > CLASS statements, which error out like:
>
>
On Feb 6, 2007, at 9:54 AM, Andrew Sullivan wrote:
On Tue, Feb 06, 2007 at 09:43:01AM -0600, Thomas F. O'Connell wrote:
DETAIL: Table has type character varying, but query expects
character varying.
In another thread, someone else is reporting this too. I'm
wondering whether something went w
> You probably want one of the mysql converter projects, e.g.
> http://pgfoundry.org/projects/mysql2pgsql/
> Also read the "converting from other databases" section here:
> http://www.postgresql.org/docs/techdocs
I tried several conversion tools and did get some minor success with one
or two b
Have you installed any updates for PostgreSQL? The latest security update
fixed something with type checks or so.
I've seen the same error message also on the BUGS mailing list concerning
a
broken CHECK constraint on a table row.
Perhaps this is the cause of the error messages.
Well, I've just
You might take a look at index anding for speeding up your selects
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Richard Huxton
Sent: Tuesday, February 06, 2007 7:24 AM
To: roopa perumalraja
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Storing
On Tue, Feb 06, 2007 at 10:59:21AM -0500, Walter Vaughan wrote:
>
> Is this still true in regards to Xeon's? I was looking at a server with
> Quad Core Xeon 2 5335 @ 2.0GHz.
Multi-core Xeons are not as affected, and are somewhat different
"under the hood". So no, you're probably ok there.
> A
On 06.02.2007, at 08:59, Walter Vaughan wrote:
Is this still true in regards to Xeon's? I was looking at a server
with Quad Core Xeon 2 5335 @ 2.0GHz.
No, it's not true anymore. See
http://tweakers.net/reviews/657/1
for an interesting comparison.
cug
---(end of bro
On Thu, Jan 25, 2007 at 12:17:52PM -0800, Ben wrote:
> familiar with Slony, and from what I understand, using Slony with bad
> networks leads to bad problems. I'm also not sure that Slony supports
> replicating from multiple sources to the same postgres install, even if
> each replication proces
"Thomas F. O'Connell" <[EMAIL PROTECTED]> writes:
> but we just built 8.2.2 from source using cc, and now we're seeing
> this type of error in the logs:
> ERROR: attribute 3 has wrong type
> DETAIL: Table has type character varying, but query expects
> character varying.
This has nothing to
Chander Ganesan wrote:
Richard Huxton wrote:
Hannes Dorbath wrote:
http://pgfoundry.org/projects/pgmemcache/
We'd like to use pgmemcache with PG 8.2. The memcached version
doesn't matter much (1.2.x is current, 1.1.x would be fine as well).
It fails to build against 8.2 with various errors.
On 06.02.2007 17:04, Richard Huxton wrote:
Chander Ganesan wrote:
Richard Huxton wrote:
Hannes Dorbath wrote:
http://pgfoundry.org/projects/pgmemcache/
We'd like to use pgmemcache with PG 8.2. The memcached version
doesn't matter much (1.2.x is current, 1.1.x would be fine as well).
It fai
On Wed, Jan 31, 2007 at 03:17:40PM -0800, Ben wrote:
> the remote sites back to the central site, each remote site needs to have
> a normal slony node first, which I don't have the hardware for.
An answer for this, though a dirty kludge, is to replicate to another
database in the same cluster. T
The FSF says the MPL is not compatible with the GPL, but, well, the FSF
generally finds **all** non-GPL licenses incompatible with the GPL (BSD,
MPL, Apache, etc.). The only truly GPL-compatible license I know of is
LGPL (and there have been arguments about that). That’s the problem
with the
On Tue, 2007-02-06 at 10:19, Tim Tassonis wrote:
> > The FSF says the MPL is not compatible with the GPL, but, well, the FSF
> > generally finds **all** non-GPL licenses incompatible with the GPL (BSD,
> > MPL, Apache, etc.). The only truly GPL-compatible license I know of is
> > LGPL (and ther
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6 Feb 2007, at 15:59, Walter Vaughan wrote:
I need to purchase a new server to put posgresql on that will be
acting as the DBMS server for Apache ofBiz soon. While googling
around for performance tweaks I saw this at http://revsys.com/
writi
Jim C. wrote:
You probably want one of the mysql converter projects, e.g.
http://pgfoundry.org/projects/mysql2pgsql/
Also read the "converting from other databases" section here:
http://www.postgresql.org/docs/techdocs
I tried several conversion tools and did get some minor success with one
On Tue, 2007-02-06 at 10:33, Lars Heidieker wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> On 6 Feb 2007, at 15:59, Walter Vaughan wrote:
>
> > I need to purchase a new server to put posgresql on that will be
> > acting as the DBMS server for Apache ofBiz soon. While googling
Hi all
When examining strange behaviour in one of my programs I found out that
I must have somehow gotten into a timeout situation when fetching rows
from a cursor. My program read the first row, did some stuff for six
minutes and then tried to fetch the second row, which failed. The
connecti
"PostgreSQL 8.2.0 on i386-portbld-freebsd6.0, compiled by GCC cc (GCC) 3.4.4
[FreeBSD] 20050518"
We just switched from 'pg_dumpall" to "pg_dump -format=c" for our nightly
backups.
I wanted to experiment with restoring a single table (if the need should ever
arise) from the dump file.
I use the
I have a table with a few million rows which has inserts performed on it
roughly 50 or so times a minute. It contains a heavily-queried column
that I would like to add an index to, but I am concerned about a
deadlock occurring. Should I wait until downtime to add the index, or
is the Postgres
On Tuesday 06 February 2007 09:32, Jeff Amiel <[EMAIL PROTECTED]>
wrote:
> We just switched from 'pg_dumpall" to "pg_dump -format=c" for our nightly
> backups. I wanted to experiment with restoring a single table (if the
> need should ever arise) from the dump file.
> I also notice that the index
Tim Tassonis <[EMAIL PROTECTED]> writes:
> When examining strange behaviour in one of my programs I found out that
> I must have somehow gotten into a timeout situation when fetching rows
> from a cursor. My program read the first row, did some stuff for six
> minutes and then tried to fetch the
On Feb 6, 10:33 am, [EMAIL PROTECTED] (Tom Lane) wrote:
> "Thomas F. O'Connell" <[EMAIL PROTECTED]> writes:
>
> > but we just built 8.2.2 from source using cc, and now we're seeing
> > this type of error in the logs:
> > ERROR: attribute 3 has wrong type
> > DETAIL: Table has type character vary
On Tuesday 06 February 2007 09:38, John McCawley <[EMAIL PROTECTED]>
wrote:
> I have a table with a few million rows which has inserts performed on it
> roughly 50 or so times a minute. It contains a heavily-queried column
> that I would like to add an index to, but I am concerned about a
> deadl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/06/07 10:59, Scott Marlowe wrote:
> On Tue, 2007-02-06 at 10:19, Tim Tassonis wrote:
[snip]
>> It's been said a million times by BSD advocats: put one line of code
>> under GPL and you instantly become a willingless slave of Richard
>> Stallman
Hi Tom
Tom Lane wrote:
Tim Tassonis <[EMAIL PROTECTED]> writes:
When examining strange behaviour in one of my programs I found out that
I must have somehow gotten into a timeout situation when fetching rows
from a cursor. My program read the first row, did some stuff for six
minutes and then
Tim Tassonis <[EMAIL PROTECTED]> writes:
> I try to reproduce the situation tomorrow and will also check on any
> odbc_errmsg() messages and the postmaster log.
OK. A couple of comments: the only timeout within Postgres itself is
statement_timeout, which I think wouldn't apply to your situation
On Tue, Feb 06, 2007 at 10:09:16AM -0500, Michael Slattery wrote:
> When does this error crop up? What is the query? Does this select
> involve more than one table, or does it involve any homemade
> functions? Or overriden functions?
My application broke in a big way with the security updat
Thomas F. O'Connell wrote:
> On Feb 6, 10:33 am, [EMAIL PROTECTED] (Tom Lane) wrote:
> > "Thomas F. O'Connell" <[EMAIL PROTECTED]> writes:
> >
> > > but we just built 8.2.2 from source using cc, and now we're seeing
> > > this type of error in the logs:
> > > ERROR: attribute 3 has wrong type
From the FAQ:
1.14) Will PostgreSQL handle recent daylight saving time changes
in various countries?
PostgreSQL versions prior to 8.0 use the operating system's
timezone database for daylight saving information. All current
versions of PostgreSQL 8.0 and later contain up-
Andrea Arcangeli wrote:
> On Tue, Feb 06, 2007 at 10:09:16AM -0500, Michael Slattery wrote:
> > When does this error crop up? What is the query? Does this select
> > involve more than one table, or does it involve any homemade
> > functions? Or overriden functions?
>
> My application broke
On Tue, Feb 06, 2007 at 01:19:28PM -0500, Bruce Momjian wrote:
> This is a known bug in 8.2.2 and we are discussing methods of
> distributing the fix as quickly as possible.
Ok great! Take your time, thanks.
---(end of broadcast)---
TIP 3: Have you
Bruce Momjian wrote:
> Andrea Arcangeli wrote:
> > Actually I'm using the REL8_2_STABLE branch in CVS which may be a bit
> > more advanced than the plain 8.2.2, but still it's supposedly a stable
> > branch.
> >
> > The easiest way for me to reproduce is this:
> >
> > cpushare=> create table x (
On Tuesday 06 February 2007 13:16, Ed L. wrote:
> From the FAQ:
>
>
> 1.14) Will PostgreSQL handle recent daylight saving time changes
> in various countries?
>
> PostgreSQL versions prior to 8.0 use the operating system's
> timezone database for daylight saving information. Al
Ed L. wrote:
>
> >From the FAQ:
>
>
> 1.14) Will PostgreSQL handle recent daylight saving time changes
> in various countries?
>
> PostgreSQL versions prior to 8.0 use the operating system's
> timezone database for daylight saving information. All current
> versions of Po
Steve Crawford wrote:
> > I was trying to avoid getting into the gory details of which releases
> > had which timezone fixes, but it seems I can't avoid it. The new FAQ
> > item has the details:
> >
> > USA daylight saving time changes are included in PostgreSQL release
> > 8.0.[4+], and
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Steve Crawford wrote:
>> 1. What, exactly, was the point of moving away from the system zoneinfo
>> files and requiring PG admins to maintain yet another apparently
>> identical set of files?
The fact that not all systems use the zic database. We were t
Bruce Momjian wrote:
> USA daylight saving time changes are included in PostgreSQL
> release 8.0.[4+], and all later major releases, e.g. 8.1. Canada and
> Western Australia changes are included in 8.0.[10+], 8.1.[6+], and
> all later major releases. PostgreSQL releases prior to 8.0 use the
>
Peter Eisentraut wrote:
> Bruce Momjian wrote:
> > USA daylight saving time changes are included in PostgreSQL
> > release 8.0.[4+], and all later major releases, e.g. 8.1. Canada and
> > Western Australia changes are included in 8.0.[10+], 8.1.[6+], and
> > all later major releases. PostgreS
> I was trying to avoid getting into the gory details of which releases
> had which timezone fixes, but it seems I can't avoid it. The new FAQ
> item has the details:
>
> USA daylight saving time changes are included in PostgreSQL release
> 8.0.[4+], and all later major releases, e.g. 8.1
> On 02/06/07 10:59, Scott Marlowe wrote:
>> On Tue, 2007-02-06 at 10:19, Tim Tassonis wrote:
> [snip]
>>> It's been said a million times by BSD advocats: put one line of code
>>> under GPL and you instantly become a willingless slave of Richard
>>> Stallmans hoards of children-eating communists.
On Tue, 6 Feb 2007, Walter Vaughan wrote:
CPUs ? The more CPUs the better, however if your database does not use many
complex functions your money is best spent on a better disk subsystem. Also,
avoid Intel Xeon processors with PostgreSQL as there is a problem with the
context switching in t
around 6:30 this morning, I started getting the following messages in my log:
Feb 6 06:33:34 mojo postgres[1117]: [2-1] :: ERROR: could not access
status of transaction 51911
Feb 6 06:34:35 mojo postgres[1128]: [2-1] :: ERROR: could not access
status of transaction 51911
[...]
repeat
On 2/6/07, Merlin Moncure <[EMAIL PROTECTED]> wrote:
around 6:30 this morning, I started getting the following messages in my log:
Feb 6 06:33:34 mojo postgres[1117]: [2-1] :: ERROR: could not access
status of transaction 51911
Feb 6 06:34:35 mojo postgres[1128]: [2-1] :: ERROR: could no
Merlin Moncure wrote:
> On 2/6/07, Merlin Moncure <[EMAIL PROTECTED]> wrote:
>> around 6:30 this morning, I started getting the following messages in
>> my log:
>>
>> Feb 6 06:33:34 mojo postgres[1117]: [2-1] :: ERROR: could not access
>> status of transaction 51911
>> Feb 6 06:34:35 mojo po
Merlin Moncure wrote:
> On 2/6/07, Merlin Moncure <[EMAIL PROTECTED]> wrote:
> >around 6:30 this morning, I started getting the following messages in my
> >log:
> >
> >Feb 6 06:33:34 mojo postgres[1117]: [2-1] :: ERROR: could not access
> >status of transaction 51911
> >Feb 6 06:34:35 mojo
On 2/6/07, Stefan Kaltenbrunner <[EMAIL PROTECTED]> wrote:
Merlin Moncure wrote:
> On 2/6/07, Merlin Moncure <[EMAIL PROTECTED]> wrote:
>> around 6:30 this morning, I started getting the following messages in
>> my log:
>>
>> Feb 6 06:33:34 mojo postgres[1117]: [2-1] :: ERROR: could not access
On 2/6/07, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> actually, here is some more relevant bits from the log.
> Feb 6 06:31:33 mojo postgres[1088]: [1-1] :: LOG: autovacuum:
> processing database "template0"
> Feb 6 06:31:33 mojo postgres[1088]: [2-1] :: ERROR: could not access
> status of t
Yeah, log shipping looks like it solves the network problem, except for
the part about how how I must replicate to a normal slony node before I
can get logs to ship. We don't have the hardware to have a secondary
database at every site. :(
On Tue, 6 Feb 2007, Andrew Sullivan wrote:
On Thu, J
Merlin Moncure wrote:
> ya, it doesn't seem to match, as this seems to be repeating quite
> regularly. interesting that my 'clog' files start at 06B6 and count
> up. 0207 is way off the charts.
>
> a lot of applications are hitting this database, and so far everything
> seems to be running ok (i
n 2/6/07, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
Merlin Moncure wrote:
> ya, it doesn't seem to match, as this seems to be repeating quite
> regularly. interesting that my 'clog' files start at 06B6 and count
> up. 0207 is way off the charts.
>
> a lot of applications are hitting this databa
Merlin Moncure wrote:
> On 2/6/07, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> >> actually, here is some more relevant bits from the log.
> >> Feb 6 06:31:33 mojo postgres[1088]: [1-1] :: LOG: autovacuum:
> >> processing database "template0"
> >> Feb 6 06:31:33 mojo postgres[1088]: [2-1] :: ERRO
Merlin Moncure wrote:
> n 2/6/07, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> >Merlin Moncure wrote:
> >
> >> ya, it doesn't seem to match, as this seems to be repeating quite
> >> regularly. interesting that my 'clog' files start at 06B6 and count
> >> up. 0207 is way off the charts.
> >>
> >> a
> If there´s only the insert_850 RULE then everything works as expected -
> the
> insert prints "INSERT 0 0", the row is inserted into the correct partition
> which is sessions_850 - I can fetch it using either
>
> SELECT * FROM sessions WHERE id = currval('sessions_id_seq');
>
> or dire
Is it possible to configure the tsearch2 parser? I'd like a very dumb
parser that splits on everything that is not [a-zA-Z0-9.]. The
default parser seems to work well on my dataset except for the '/'
character ... it doesn't split mike/john into two lexemes. And ideas?
Thanks!
---
Shouldn't there be an announcement about the buggy 8.2.2 announced
yesterday preceding the availability of new binaries, or is the bug
not considered severe enough to invalidate the 8.2.2 sources that are
currently in distribution?
--
Thomas F. O'Connell
optimizing modern web applications
On Tue, 2007-02-06 at 11:59, Ron Johnson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 02/06/07 10:59, Scott Marlowe wrote:
> > On Tue, 2007-02-06 at 10:19, Tim Tassonis wrote:
> [snip]
> >> It's been said a million times by BSD advocats: put one line of code
> >> under GPL and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/06/07 14:51, Scott Marlowe wrote:
> On Tue, 2007-02-06 at 11:59, Ron Johnson wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 02/06/07 10:59, Scott Marlowe wrote:
>>> On Tue, 2007-02-06 at 10:19, Tim Tassonis wrote:
>> [snip]
>
>> With all their talk about "community this" and "community that",
>> what else could they be but communists?
>
> I think you missed my joke there...
Yeah, Ron Johnson wrote me about that already. Sorry for that, I'm
probably too touchy when it comes to marking someone as a communist,
especially
Thomas F. O'Connell wrote:
> Shouldn't there be an announcement about the buggy 8.2.2 announced
> yesterday preceding the availability of new binaries, or is the bug
> not considered severe enough to invalidate the 8.2.2 sources that are
> currently in distribution?
The sources and binaries
Jim C. wrote:
Richard Huxton wrote:
Jim C. wrote:
You probably want one of the mysql converter projects, e.g.
http://pgfoundry.org/projects/mysql2pgsql/
Also read the "converting from other databases" section here:
http://www.postgresql.org/docs/techdocs
I tried several conversion tools an
On 2/6/07, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
Merlin Moncure wrote:
> On 2/6/07, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> >> actually, here is some more relevant bits from the log.
> >> Feb 6 06:31:33 mojo postgres[1088]: [1-1] :: LOG: autovacuum:
> >> processing database "template0"
I'm doing some testing on a larger dataset, and I've started getting a
57014 error message when I catch an NpgsqlException. I thought it
might be timing out on me, so in the connection string I've set the
time out settings to the maximum of 1024 seconds before timeout.
Has anyone else experienced
I have a web site devoted to quest guides for World of Warcraft
players. There is a view that gets all the data needed for the quest
details page from several tables. The view currently looks like this
(joins indicating non-null columns and left joins indicating nullable
columns):
SELECT q.id, q.
did a pg_dump --format=c for a production database (on a 8.1.2 server) and
attempted to pg_restore on a 8.2.0 server.
Things seemed to go fine with the exception of functions, triggers and trigger
functions.
It was apparently doing a bunch of ACL work towards the end and spewed a slew
of error
The original pg_dump used --schema="public" .
Could the fact that pg_catalog or information_schema weren't included cause
these kinds of issues? (I can't imagine why)
<[EMAIL PROTECTED]> wrote: did a pg_dump --format=c for a production database
(on a 8.1.2 server) and attempted to pg_restore
Ged <[EMAIL PROTECTED]> writes:
> SELECT
> q.id, q.name, q.summary, q.instructions, q.experience, q.notes,
> q.starts, q.ends
> , q.stage, st.description
> , q.series, r.name
> , COALESCE('../zones/' || q.zone, '../instances/' || q.instance)
> , COALESCE(z.name, i.name)
> INTO
Jeff Amiel <[EMAIL PROTECTED]> writes:
> did a pg_dump --format=c for a production database (on a 8.1.2 server) and
> attempted to pg_restore on a 8.2.0 server.
> Things seemed to go fine with the exception of functions, triggers and
> trigger functions.
Seems pretty strange. Can you strip thi
Jeff Amiel <[EMAIL PROTECTED]> writes:
> The original pg_dump used --schema="public" .
I think that would have excluded anything that didn't demonstrably
belong to schema public, such as procedural languages. Is it possible
that *all* your functions failed to load, and you only noted the ensuing
1 - 100 of 112 matches
Mail list logo