Garry Saddington wrote:
> I have the following error:
>
> Postgres 8.3 via psycopg 1.1.21 and zope 2.10.
>
> 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 more a general programming question rather than a pg
question but maybe some postgresql features may offer a better
solution.
I'd describe the problem from an OO point of view and I'd like to
know how I could obtain a similar solution with postgresql.
If I have a hierarchy of classes, som
I have a partitioned table that uses monthly temporal partitions.
Every night I want to load the last 10 weeks of data into a separate
non-partitioned table.
Currently, I truncate the destination table, drop the indexes,
execute:
"INSERT INTO destination SELECT * FROM source_partition"
and recreat
On Tue, June 24, 2008 8:41 am, Adrian Moisey wrote:
> Hi
>
> We have a 100GB database (16GB dumped) running on 8.2.
>
> Since the bandwidth in South Africa isn't that freely available it is
> difficult for us to get a new copy of out DB in our office (our fastest
> link in the office is 4Mbps).
>
>
Hallo fellows
i am new user of postgresql and need ur help to understand it.I am now using
postgresql 3.0 with Microsoft Visual C++ 2005 express edition.But i can't
connect MV C++ with postgresql.There is always library failure.
Pls help me. I have installed all on window XP.
salman
___
Hello there
Can anyone please tell me how to make a column uneditable..
Plz give me some output
thans
hello
2008/6/24 kartik <[EMAIL PROTECTED]>:
> Hello there
>
> Can anyone please tell me how to make a column uneditable….
>
> Plz give me some output
>
> thans
try trigger
create table foo(
a varchar
);
create function a_update_trg()
returns trigger as $$
begin
if new.a is distinct from ol
am Tue, dem 24.06.2008, um 15:19:46 +0530 mailte kartik folgendes:
> Hello there
>
> Can anyone please tell me how to make a column uneditable?.
You can write a TRIGGER to avoid changes on the column. Within the
TRIGGER you can compare OLD.column with NEW.column and there you can
raise an error
Perhaps trivial, but:
Additional to or instead of triggers You can use grants to allow updates only
to special users.
Ludwig
>Hello there
>
>Can anyone please tell me how to make a column uneditable..
>
>Plz give me some output
>
>thans
>
--
Sent via pgsql-general mailing list (pgsql-general@
Nikola <[EMAIL PROTECTED]> writes:
> Currently, I truncate the destination table, drop the indexes,
> execute:
> "INSERT INTO destination SELECT * FROM source_partition"
> and recreate indexes.
> This loads about 66.5 million rows into the destination table in about
> 1 hour. Recreating of indexes
I just upgraded to 8.3.3 from 8.1.5 and noticed that backslashes are
handled completely differently now. For example,
db=# insert into junk (cifs) values ('\\f\bar');
WARNING: nonstandard use of \\ in a string literal
LINE 1: insert into junk (cifs) values ('\\f\bar');
"Brandon Metcalf" <[EMAIL PROTECTED]> writes:
> I just upgraded to 8.3.3 from 8.1.5 and noticed that backslashes are
> handled completely differently now. For example,
See standard_conforming_strings and escape_string_warning.
regards, tom lane
--
Sent via pgsql-general
b == [EMAIL PROTECTED] writes:
b> I just upgraded to 8.3.3 from 8.1.5 and noticed that backslashes are
b> handled completely differently now. For example,
It looks like the default for escape_string_warning is now "on".
However, it says in the docs that future versions will treat the
backslas
t == [EMAIL PROTECTED] writes:
t> "Brandon Metcalf" <[EMAIL PROTECTED]> writes:
t> > I just upgraded to 8.3.3 from 8.1.5 and noticed that backslashes are
t> > handled completely differently now. For example,
t> See standard_conforming_strings and escape_string_warning.
Excellent. I had mi
Adam Rich wrote:
> One interesting example is having rules and triggers watching for
> deletes or updates on a table. If many rows are modified, rules
> can be faster. Take this statement:
>
> DELETE FROM mydata WHERE idval BETWEEN 1 and 2;
>
> Say this statement deletes 10,000 rows.
-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 big distros keep all that up to date with Pos
"Brandon Metcalf" <[EMAIL PROTECTED]> writes:
> t == [EMAIL PROTECTED] writes:
> t> See standard_conforming_strings and escape_string_warning.
> Excellent. I had missed the standard_conforming_strings and will turn
> this on. Hold on. Yes, that did it. Thanks so much.
Well, if your intent is
Initdb throws "could not select a suitable default timezone" on PostgreSQL
8.3.3
and Windows x64.
We'd like to use those settings --lc-collate=C --lc-ctype=French_Canada
pginstaller does initdb properly but not with the parameters we want.
We want upper, lower, regex, ... to process acccented c
On Mon, Jun 23, 2008 at 11:54 PM, Adam Rich <[EMAIL PROTECTED]> wrote:
>> Can you describe, or point me to somewhere which describes, all the
>> things you can do with a rule that you can't do with a trigger? The
>> only examples of rules in the manual are (1) logging, which I've just
>> been told
On Tue, Jun 24, 2008 at 10:28:00AM -0500, Michael Shulman wrote:
> I have read the manual. As I pointed out, the only examples of rules
> in the manual are (1) something which may be better done with a
> trigger, and certainly *can* be done with a trigger, whatever the
> speed considerations may b
Martijn van Oosterhout <[EMAIL PROTECTED]> writes:
> On Tue, Jun 24, 2008 at 10:28:00AM -0500, Michael Shulman wrote:
>> My question was, what else *can* you do with a rule that you *can't*
>> do with a trigger? Are rules only a way to speed up things that could
>> also be done with triggers?
> W
We've got a .NET application that's trying to move data from an old MySQL
database to a shiny new Postgres db, but we keep getting this error:
invalid byte sequence for encoding "UTF8": 0xf66a6e69
The MySQL table is using "latin1 -- cp1252 West European" and the Postgres
server is using UTF8.
t == [EMAIL PROTECTED] writes:
t> "Brandon Metcalf" <[EMAIL PROTECTED]> writes:
t> > t == [EMAIL PROTECTED] writes:
t> > t> See standard_conforming_strings and escape_string_warning.
t> > Excellent. I had missed the standard_conforming_strings and will turn
t> > this on. Hold on. Yes, th
"Brandon Metcalf" <[EMAIL PROTECTED]> writes:
> t == [EMAIL PROTECTED] writes:
> t> Well, if your intent is to replicate 8.1's behavior, you should instead
> t> frob the other switch.
> I now have
> escape_string_warning = off
> and
> standard_conforming_strings = on
> in postgresql.conf and
On Tue, Jun 24, 2008 at 11:31:16AM -0500, Ryan Wells wrote:
> Subject: [GENERAL] String Encoding Conversion Problem
>
> We've got a .NET application that's trying to move data from an old MySQL
> database to a shiny new Postgres db, but we keep getting this error:
> invalid byte sequence for enc
t == [EMAIL PROTECTED] writes:
t> "Brandon Metcalf" <[EMAIL PROTECTED]> writes:
t> > t == [EMAIL PROTECTED] writes:
t> > t> Well, if your intent is to replicate 8.1's behavior, you should
instead
t> > t> frob the other switch.
t> > I now have
t> > escape_string_warning = off
t> > and
On Tuesday 24 June 2008 11:30:14 David Siebert wrote:
> 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 big distros keep all that up to
On Tue, Jun 24, 2008 at 8:30 AM, David Siebert <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Which disto is best for running a Postgres server?
That is the subject of many a holy flame war. FreeBSD 7.0 seems to
currently be regarded as being one of the top perfo
"Brandon Metcalf" <[EMAIL PROTECTED]> writes:
> t == [EMAIL PROTECTED] writes:
> t> Uh, no, that is certainly *not* the behavior you were getting in 8.1;
> t> 8.1's behavior corresponds to both switches off.
> OK. I'm confused. With 8.1.5 we never had to do anything special
> with backslashes.
Jorge Godoy <[EMAIL PROTECTED]> writes:
> On Tuesday 24 June 2008 11:30:14 David Siebert wrote:
>> I was wondering if anybody has made an Postgres centric distro?
> I'm running OpenSuSE 11.0 and I have PostgreSQL 8.3.1 right from the
> installation DVD.
Fedora 9 likewise shipped with PG 8.3.1.
At 2:12p -0400 on Tue, 24 Jun 2008, Tom Lane wrote:
> Jorge Godoy <[EMAIL PROTECTED]> writes:
>> On Tuesday 24 June 2008 11:30:14 David Siebert wrote:
>>> I was wondering if anybody has made an Postgres centric distro?
>
>> I'm running OpenSuSE 11.0 and I have PostgreSQL 8.3.1 right from the
>> i
t == [EMAIL PROTECTED] writes:
t> "Brandon Metcalf" <[EMAIL PROTECTED]> writes:
t> > t == [EMAIL PROTECTED] writes:
t> > t> Uh, no, that is certainly *not* the behavior you were getting in 8.1;
t> > t> 8.1's behavior corresponds to both switches off.
t> > OK. I'm confused. With 8.1.5 we
On Tue, 24 Jun 2008, Kevin Hunter wrote:
Short of a response, I've read a number of reports that given some
tuning FreeBSD 7.0 is the current top performer.
Those reports are all not quite right and I'm trying to get time to fully
debunk them in PostgreSQL land.
First off, they were running
I found a similar problem only with a slight variation.
postgresql, for me, is installed in /opt/local/ with the particular file
being located at:
/opt/local/lib/postgresql83/libpq.5.dylib
This is all a part of the mac ports installation for apache2 and postgres.
It seems that the problem isn
is there a way to find out / calculate / estimate how big a pg_dump
using plain text format for a DB will be ?
I have this system with a 7.4 version and a DB that is over 60GB and I
know that the admins have never done a vacuum there.
The system only has about 20GB of free space so I don't want
explain select * from d_trr where revision like '^B2.%.SX'
--where ast_revision = 'B2.M.SX'
Seq Scan on d_trr (cost=0.00..2268460.98 rows=1 width=16)
Filter: ((revision)::text ~~ '^B2.%.SX'::text)
show lc_collate;
en_US.UTF-8
Is it that this is handled by tsearch2? Or I need to do the locale
Ow Mun Heng wrote:
explain select * from d_trr where revision like '^B2.%.SX'
--where ast_revision = 'B2.M.SX'
Seq Scan on d_trr (cost=0.00..2268460.98 rows=1 width=16)
Filter: ((revision)::text ~~ '^B2.%.SX'::text)
show lc_collate;
en_US.UTF-8
Is it that this is handled by tsearch2? Or I
--On Tuesday, June 24, 2008 10:30:14 AM -0400 David Siebert
<[EMAIL PROTECTED]> wrote:
Which disto is best for running a Postgres server?
I run most of my postgres servers on Debian. I really love it, because
once a new major version comes out you can very easy install it
parallel to your
Hi
Take a look also on Londiste from SkyTools. It is easy to set up and manage.
In addition SkyTools contains other useful scripts and tools.
We use Londiste to replicate data ovwe WAN where walshipping would consume
too much bandwidth.
Asko
On Tue, Jun 24, 2008 at 9:41 AM, Adrian Moisey <[EMAIL
On Wed, 2008-06-25 at 14:58 +1000, Klint Gore wrote:
> Ow Mun Heng wrote:
> > explain select * from d_trr where revision like '^B2.%.SX'
> > --where ast_revision = 'B2.M.SX'
> >
> > Seq Scan on d_trr (cost=0.00..2268460.98 rows=1 width=16)
> > Filter: ((revision)::text ~~ '^B2.%.SX'::text)
> >
Re-reading the documentation, and I have the answer. If adding a
tsvector column, then for per row selection, I should also add a second
column of type regconfig to specify the language that rows contents are in.
Cheers,
Andy
Andrew wrote:
Apologies if this question has been previously cover
Apologies if this question has been previously covered, but I was not
able to find something similar in any of the mailing list archives.
With full text search, if you need to support a table where the content
of individual tuples/rows may be in different languages with the
language of the con
42 matches
Mail list logo
