Neil Dugan wrote:
On Tue, 2005-04-12 at 08:51 +0100, Richard Huxton wrote:
Inpreet Singh wrote:
syslog = 2 # range 0-2
syslog_facility = 'LOCAL0'
syslog_ident = 'postgres'
You also need to update your syslog.conf and restart syslogd
Add a line like:
local0.*
On 4/12/05, Matt Van Mater [EMAIL PROTECTED] wrote:
I've been experimenting with loading a large amount of data into a
fairly simple database using both psql and perl prepared statements.
Unfortunately I'm seeing no appreciable differences between the two
methods, where I was under the
On Apr 13, 2005, at 4:12 AM, Dawid Kuroczko wrote:
On 4/12/05, Matt Van Mater [EMAIL PROTECTED] wrote:
I've been experimenting with loading a large amount of data into a
fairly simple database using both psql and perl prepared statements.
Unfortunately I'm seeing no appreciable differences between
On Wednesday 13 April 2005 01:21, Jinane Haddad wrote:
Thanx guys for the advices.
i think i will have to find some POLITICAL approach in order to
restructure the existing database, which i am not so good at but worse
trying. Note that even the code is Bad (they are using PHP for a big
Dawid Kuroczko wrote:
For a test you might want to try also this approach (both from perl and
from psql):
$dbh-do('PREPARE sth_tim (int,inet,boolean,timestamptz) AS INSERT
INTO timestamps VALUES ($1,$2,$3,$4)');
$sth_tim = $dbh-prepare(EXECUTE sth_tim(?,?,?,?));
...and later execute it. (and
Thanks to all who replied. Thanks for the tip on that last thread
Tom, I don't know how I missed it. I have a hunch that it's not
applicable to me at this time because I'm running a year and a half
old software (included in OpenBSD 3.4), but I will have to check which
version of DBD::Pg was
On Wed, Apr 13, 2005 at 09:57:09 -0400,
Matt Van Mater [EMAIL PROTECTED] wrote:
Also, I forgot to mention earlier that I tried using transactions to
speed things up, but since I expect to see certain inserts fail I
would need to rework my code so the whole transaction doesn't fail if
one
On Apr 12, 2005, at 4:48 PM, Tom Lane wrote:
James Robinson [EMAIL PROTECTED] writes:
insert into simple_table values (null, '(43)'); -- GRR works!!! It'll
let any smallint in. What happened to the constraint?
The composite-type input routine doesn't check any constraints ...
and that includes
Neil Conway wrote:
For an INSERT query without any sub-selects
that is not rewritten by any rules, the cost to parse, rewrite and plan
the statement is trivial. So I wouldn't expect prepared statements to be
a big win -- you would gain a lot more from batching multiple inserts
First of all, hi. I'm new to this mailing list.
I searched this on the net, but I didn't get any usable answers...
So here's my problem:
I have 2 schemas. One is called SITE, one SITE_forum.
What I wanted, is to separate the forum from the whole Site db, so I can
put them on different
Neil Conway [EMAIL PROTECTED] writes:
The intent of prepared statements is to reduce the overhead of running
the parser, rewriter and planner multiple times for a statement that is
executed multiple times. For an INSERT query without any sub-selects
that is not rewritten by any rules, the
On Wed, Apr 13, 2005 at 13:54:05 +0200,
Matthias Loitsch [EMAIL PROTECTED] wrote:
So I thought I could make a foreign key on a different Schema (db), and
use the same table
And well, thats where I started to search if this is possible ... and,
in fact my main question is: Is this a
Thank you. I'm used to installing from source or Debian packages. I
haven't poked around too much at the console level of the Mac. I would
assume I install from source and just point the install to the old data
directory? Any gotchas to watch for that aren't in the manual? I would
assume I
On Apr 13, 2005, at 9:57 AM, Matt Van Mater wrote:
Thanks to all who replied. Thanks for the tip on that last thread
Tom, I don't know how I missed it. I have a hunch that it's not
applicable to me at this time because I'm running a year and a half
old software (included in OpenBSD 3.4), but I
Greetings,
PostgreSQL 8.0.1 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.3.2.
When I run
select * from table1;
I got an error:
=
ERROR: could not convert UTF-8 character 0x00e9 to ISO8859-1
I tried to google but cannot find much info about it. Can somebody help?
Thanks,
Emi
James Robinson [EMAIL PROTECTED] writes:
Thank you for the great info. If I may, here's another question. I am in
the need of new scalar types, essentially domain'd smallints, hence
why my composite type had but one composite member. Domain'd
smallints would be great, but it seems when they
On Wed, Apr 13, 2005 at 09:57:09AM -0400, Matt Van Mater wrote:
Also, I forgot to mention earlier that I tried using transactions to
speed things up, but since I expect to see certain inserts fail I
would need to rework my code so the whole transaction doesn't fail if
one insert goes bad.
Will inherits helps you ?
create table SITE_forum.t1 () inherits (SITE.t);
Oleg
On Wed, 13 Apr 2005, Matthias Loitsch wrote:
First of all, hi. I'm new to this mailing list.
I searched this on the net, but I didn't get any usable answers...
So here's my problem:
I have 2 schemas. One is called
Mac OSX 10.4 aka Tiger is going to be released in a couple of weeks,
does
anyone know if Tiger will still be Postgresql friendly?
Jerry
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
Jerry LeVan wrote:
Mac OSX 10.4 aka Tiger is going to be released in a couple of weeks, does
anyone know if Tiger will still be Postgresql friendly?
There is no reason to think that it wouldn't be.
Sincerely,
Joshua D. Drake
Jerry
---(end of
On Wed, Apr 13, 2005 at 01:21:41PM -0400, Jerry LeVan wrote:
Mac OSX 10.4 aka Tiger is going to be released in a couple of weeks,
does
anyone know if Tiger will still be Postgresql friendly?
8.0.2 doesn't build out of the box on build 8A351B. I've not had a chance
to see what's going on yet,
On Apr 13, 2005, at 1:52 PM, Steve Atkins wrote:
8.0.2 doesn't build out of the box on build 8A351B. I've not had a
chance
to see what's going on yet, but it doesn't look like anything too hard
to fix.
My guess would be any issues on building would be related to gcc4 in
tiger, and any changes
Specify your codepage :
SET CLIENT_ENCODING TO 'LATIN1' ;
SELECT * FROM table1 ;
Your database woul be coded as LATIN1.
Luc
- Original Message -
From: Ying Lu [EMAIL PROTECTED]
To: pgsql-general@postgresql.org
Sent: Wednesday, April 13, 2005 5:49 PM
Subject: [GENERAL] About ERROR: could
On Apr 13, 2005, at 11:50 AM, Tom Lane wrote:
Thank you for the great info. If I may, here's another question. I am
in
the need of new scalar types, essentially domain'd smallints, hence
why my composite type had but one composite member. Domain'd
smallints would be great, but it seems when they
Hello,
Actually, both the server and client sides have been setup encoding
latin1.
I am trying to read data from one DB and save to another DB. When I
tried to read data from one DB (using postgresql-8.0-310.jdbc3.jar), it
seems that I lost all my French characters (they become ?).
Also, I am
unsubscribe
LIBIA ANDREA RAMOS SÁNCHEZ
INGENIERO DE SISTEMAS
ESCUELA COLOMBIANA DE INGENIERIA
CEL. 3103271242
OFC. 5452799 - 2550469 CMN-Consulting
_
Charla con tus amigos en línea mediante MSN Messenger:
Luc,
You are right. I am afraid that I checked different mahine's
client_encoding, which have been setup the correct encodings.
While for my working environment, I have
CLIENT_ENCODING = SQL_ASCII ;
SERVER_ENCODING = SQL_ASCII;
After we setup the correct encoding for client and server side, we
Mac OSX 10.4 aka Tiger is going to be released in a couple of weeks,
does
anyone know if Tiger will still be Postgresql friendly?
Well, considering that PostgreSQL is now used by Apple Remote Desktop, for
storing client-management kinds of info, I expect there will be some way to
get it
On 4/13/05, Vivek Khera [EMAIL PROTECTED] wrote:
My guess would be any issues on building would be related to gcc4 in
tiger, and any changes needed for that will be applicable to gcc4 on
any other platform too. But that's just a SWAG.
I confirmed that my postgresql 8.0.2 and 7.4.7 packages
On Mon, 2005-04-11 at 03:28 +0200, Daniel Verite wrote:
Florin Andrei wrote:
On MySQL, it's enough to do this:
GRANT ALL PRIVILEGES ON dbname.* TO username [IDENTIFIED BY 'password'];
On PostgreSQL, you have to give it privileges not only to the database,
but to all
30 matches
Mail list logo
