Am 01.12.2010 15:37, schrieb Rob Wultsch:
"For beginners, a useful startup option is --safe-updates (or
--i-am-a-dummy, which has the same effect). This option was introduced
in MySQL 3.23.11. It is helpful for cases when you might have issued a
DELETE FROM tbl_name statement but forgotten the WH
Am 22.11.2013 16:15, schrieb Tom Lane:
[ memo to self: never, ever accept another contrib module whose name
isn't a plain SQL identifier ]
Well, in that case and since this is a rarely used extension (I guess
so), maybe it would be the best to simply rename that extension to
uuidossp (or what
_sequences better? First convert the sequences,
and reject them in the validation stage?
Regards
Mario Weilguni
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
There's a IMO a problem with pg_restore, it should be easy to fix (I
hope - and I could try to fix it and send a patch).
* I've a dump taken from a 8.1 database
* I'm using gist and ltree
* I'm restoring to a 8.2 database
Problem:
I cannot use "-1" for performance, because some gist stuff has ch
Heikki Linnakangas schrieb:
Mario Weilguni wrote:
I cannot use "-1" for performance, because some gist stuff has changed
and the restore fails. But there seems to be no option for pg_restore to
use transactions for data restore, so it's very very slow (one million
records, ea
> (Aside: presumably we could walk thru the string destructively,
> in-place, swapping bytes; I think that would be theoretically
> quickest...)
Hmmm... I guess it will not work für UTF-8 or any other multibyte charset
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To mak
Tom Lane schrieb:
"Jonah H. Harris" <[EMAIL PROTECTED]> writes:
I've run into a couple cases now where it would be helpful to easily
assign an already-existing unique index as a primary key.
You need to present a more convincing use-case than this unsupported
assertion. There's hardly
Mike schrieb:
Hello,
I’m new to the core PostgreSQL code, so pardon the question if the
answer is really obvious, and I’m just missing it, but I’ve got a
relatively large web application that uses PostgreSQL as a back-end
database, and we’re heavily using memcached to cache frequently
acces
>
> open cursorSrc for select * from testtable;
>
> We cannot substitude "select * from testtable" with a variable.
>
> Is there another way to handle it?
>
> Thank you for your help. :-)
>
open cursorSrc for execute queryStr; should work fine
Regards
Mario Weilguni
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
d access to memory
location 0.
Best regards,
Mario Weilguni
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Marko Kreen schrieb:
On 6/16/08, Mario Weilguni <[EMAIL PROTECTED]> wrote:
Could someone using the pgcrypto extension please verify this?
SELECT encode(digest(null, 'md5'::text), 'hex');
or
SELECT digest(null, 'md5');
Takes a few seconds, and then
Marko Kreen schrieb:
On 6/16/08, Mario Weilguni <[EMAIL PROTECTED]> wrote:
Marko Kreen schrieb:
On 6/16/08, Mario Weilguni <[EMAIL PROTECTED]> wrote:
Could someone using the pgcrypto extension please verify this?
SELECT encode(digest(null, 'md5'::text
lated updates.
Best regards,
Mario Weilguni
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
I found the discussion about log compressing here:
http://archives.postgresql.org/pgsql-patches/2007-03/msg00502.php
But I cannot find the scripts (pg_compresslog/pg_decompresslog), how can I get
those? Will this work for 8.1 branch too? I want to use PITR, but archiving
over one days will gener
Am Donnerstag, 11. April 2002 17:44 schrieb Tom Lane:
> "Mario Weilguni" <[EMAIL PROTECTED]> writes:
> > And I did not find out how I can detect the large object
> > chunksize, either from getting it from the headers (include
> > "storage/large_object
>"Mario Weilguni" <[EMAIL PROTECTED]> writes:
>> And I did not find out how I can detect the large object
>> chunksize, either from getting it from the headers (include
>> "storage/large_object.h" did not work)
>
>Why not?
>
>Still
And how about getting database internals via SQL-functions - e.g. getting BLCSIZE,
LOBBLCSIZE?
-Ursprüngliche Nachricht-
Von: Tom Lane [mailto:[EMAIL PROTECTED]]
Gesendet: Montag, 15. April 2002 16:32
An: Mario Weilguni
Cc: [EMAIL PROTECTED]
Betreff: Re: [HACKERS] Inefficient handling
55 lines)? Send it to this list?
Best regards,
Mario Weilguni
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
Sorry I should've read the FAQ. I've posted the patch to pgsql-patches.
Am Dienstag, 16. April 2002 13:49 schrieb Mario Weilguni:
> I've improved the contributed vacuumlo command, now it behaves like all
> other postgres command line utilites e.g. supports -U, -p, -h, -?,
> My experience has been that logging to syslog makes postgres much
> slower.
>
> Can anyone confirm or refute this ?
Do you use synchronous write with syslog? Try to add a dash in
/etc/syslog.conf
e.g.
instead of
local3.* /var/log/syslog.postgres
use
loc
would'nt it be much better to expand pg_largeobject to have another column "src_oid"
(or similar), containing the OID of the referencing table from pg_class, and when
accessing large objects take the privilieges from the referencing class?
-Ursprüngliche Nachricht-
Von: Damon Cokenias [
I wanted to correct the patch this evening after work, and will check your changes.
Thanks!
-Ursprüngliche Nachricht-
Von: Bruce Momjian [mailto:[EMAIL PROTECTED]]
Gesendet: Mittwoch, 24. April 2002 16:03
An: Peter Eisentraut
Cc: Mario Weilguni; [EMAIL PROTECTED]
Betreff: Re: [HACKERS
Am Mittwoch, 24. April 2002 16:03 schrieb Bruce Momjian:
> OK, I have applied the following patch to fix these warnings. However,
> I need Mario to confirm these are the right changes. Thanks.
I've checked it and works fine, but the memcpy() prototype says it should be
void pointers. Will this
Isn't that what msync() is for? Or is this not portable?
-Ursprüngliche Nachricht-
Von: Tom Lane [mailto:[EMAIL PROTECTED]]
Gesendet: Dienstag, 25. Juni 2002 16:30
An: Curt Sampson
Cc: J. R. Nield; Bruce Momjian; PostgreSQL Hacker
Betreff: Re: [HACKERS] Buffer Management
Curt Sampson <
>...
> if (upper('001234') == lower('001234'))
> SELECT * FROM table
> WHERE id = '001234';
> else
> SELECT * FROM table
> WHERE upper(id) = '001234';
>
>Even without the index I guess that would have saved it a lot of work.
I'm
y minute or so and checks some
conditions, and I guess it is called while vacuum full is running too.
Best regards,
Mario Weilguni
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
> > Here are the details.
>
> Those probably aren't the same outer join queries.
I think you're right, these aren't the same, see below:
>
> > When I run the query "select yt1_name, yt1_descr, yt2_name, yt2_descr
> > from yuva_test1 left outer join yuva_test2 on yt1_id=yt2_id and yt2_name
> > =
a replacement for a view, isn't it? With a view I can do this:
create view v1 as select name, salary from workers where type <> 'MANAGEMENT';
with column permissions I must give access to all workers salary including the
management, but not with a view.
best re
above, I cannot imagine how this might happen in my
application, it's not
easy to say for sure, it's a quite complex web based content management system and not
easy to debug such
errors, because I've no clue how to trigger it reproduceable.
Best regards,
ork again. However it requires a lot of DBA
assistance to restore.
All other problems are solvable by using "pg_restore -L" and using a modified archiv
index, but IMO this should work out of the box.
Best regards,
Mario Weilguni
---(end of broad
Am Freitag, 16. August 2002 15:51 schrieben Sie:
> Mario Weilguni <[EMAIL PROTECTED]> writes:
> > Here are the problems I've encountered:
> > * pg_restore tries to create a table with ltree and ltree[] datatypes
> > before the type itself is created, so it fails.
&
I wrote this patch for my system, and it works fine. However, it's a really ugly
workaround. I can publish the source
if anybody is interested.
Am Montag, 26. August 2002 06:33 schrieb Thomas O'Dowd:
> Thanks for your feedback Stephan. Seems like a tough fix. Pitty it won't
> make it into 7.3. I
ECTED]]
Gesendet: Montag, 26. August 2002 17:29
An: Mario Weilguni
Cc: [EMAIL PROTECTED]
Betreff: Re: [HACKERS] Deadlock situation using foreign keys
(reproduceable)
On Mon, 26 Aug 2002, Mario Weilguni wrote:
> I wrote this patch for my system, and it works fine. However, it's a
> really ugly w
> > feature of that type. But random misfeatures such as the join syntax or
> > the decode() function are going to have a hard time getting accepted.
>
> But we have decode():
>
> test=> \df decode
> List of functions
>Result data type | Schema | Nam
> > The nice part is it has an varying number of arguments, and can
> > used within "sort". Very useful sometimes.
>
> With our CASE, you create a column using the CASE, then ODER BY on that
> column.
Not exactly, you have to create a column for this, and it will be in the select list.
Oracle do
fault in this format: 2002-09-02 08:51:27,223455+02
I found no way to import this database, experimenting with "set datestyle ..." did not
help. Will 7.3 really be that incompatible regarding timestamps? Or is this simply a
problem with my current locale?
Best regards,
ntouched
if not specified by hand. Maybe there are other uses for such a bitfield too, and will
help prevent an initdb for simple improvements.
Any comments?
Best regards,
Mario Weilguni
---(end of broadcast)---
TIP 6: Have you se
Am Dienstag, 3. September 2002 00:26 schrieb Peter Eisentraut:
> Mario Weilguni writes:
> > Timestamps in 7.2.x are this format: 2002-07-04 15:19:11.363562+02
> > 7.3 expects a timestamp per default in this format: 2002-09-02
> > 08:51:27,223455+02
>
> If you're no
uum calls is completly out of question and very error prone
anyway.
Regards,
Mario Weilguni
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
my applications.
Best regards,
Mario Weilguni
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Am Mittwoch, 4. September 2002 05:44 schrieb Matthew T. OConnor:
> I have been doing some poking around with this item, and I was planning on
> using the stats collector to do "intelligent" auto-vacuuming. I was
> planning on adding some new columns that account for activity that has
> taken plac
> What do other people get for this value?
>
> Keep in mind if we increase this value, we will get a more sequential
> scans vs. index scans.
With the new script I get 0.929825 on 2 IBM DTLA 5400RPM (80GB) with a 3Ware
6400 Controller (RAID-1)
Best regards,
Ma
>OK, I have a better version at:
The script is now broken, I get:
Collecting sizing information ...
Running random access timing test ...
Running sequential access timing test ...
Running null loop timing test ...
random test: 14
sequential test: 16
null timing test: 14
random_page_cost
>
> I'm stuck for strange reason!
> This is my first attempt to use pg_lo concept in my apps:
>
> ...
> Oid oid;
> PGconn* dbcon = PQconnectdb(conninfo.c_str());
> oid = lo_creat(dbcon, INV_WRITE | INV_READ);
> int pgfd = lo_open(dbcon, oid, INV_WRITE | INV_READ);
> ...
>
>
> lo_open ALWAY
essary, while for small tables 10 updates
might be sufficient.
Best regards,
Mario Weilguni
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
On 26 Sep 2002 at 14:05, Shridhar Daithankar wrote:
> Some time back I posted a query to build a site with 150GB of database. In
last
> couple of weeks, lots of things were tested at my place and there are some
> results and again some concerns.
> 2) Creating index takes huge amount of time.
>
>Well the test runs were for 10GB of data. Schema is attached. Read in fixed
>fonts..Last nullable fields are dummies but may be used in fututre and
varchars
>are not acceptable(Not my requirement). Tuple size is around 100 bytes..
>The index creation query was
>
>CREATE INDEX index1 ON tablenam
t tablespace.
Best regards,
Mario Weilguni
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
odify semantics.
Regards,
Mario Weilguni
icomedias graz . berlin
---
icomedias ist Hersteller von ico>>cms: Information-
und Content Management System für Inter- UND INTRAnet
-------
Mario
I noticed some other minor differences between 7.2 and 7.3:
* 7.2: select now() + '1 minute'::timespan => works
* 7.2: select now() + '1 minute'::reltime => works
* 7.3: select now() + '1 minute'::timespan => does not work (Type "timespan" does not
exist)
* 7.3 select now() + '1 minute'::reltime
false.
Regards,
Mario Weilguni
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
I'll use
indexing when I rewrite my queries to:
select 1 from mytable where id::text=''
Regards,
Mario Weilguni
-- Weitergeleitete Nachricht --
Subject: [HACKERS] int type problem in 7.3
Date: Wed, 2 Oct 2002 08:31:45 +0200
From: Mario Weilguni &
that behavior is surely non-compliant with
>the SQL spec.
No, oracle accepts this and works correctly with number() datatype.
However I did not know that in postgres '' was treated as '0'.
Regards,
Mario Weilguni
---(end of broadcast)--
It's just a cosmetic change, fixes the help screen. Should be applied in
/contrib/vacuumlo
Regards,
Mario Weilguni
--- ../vacuumlo.c Thu Sep 5 23:19:13 2002
+++ vacuumlo.c Wed Oct 2 18:03:29 2002
@@ -383,7 +383,6 @@
fprintf(stdout, " -U username\tUsername
This small patch adds a Makefile for /contrib/reindexdb/ and renames the README to
README.reindexdb.
Regards,
Mario Weilguni
diff -Nur postgresql-7.3b2.orig/contrib/reindexdb/Makefile postgresql-7.3b2/contrib/reindexdb/Makefile
--- postgresql-7.3b2.orig/contrib/reindexdb/Makefile
mm. hh24:mi:ss') into s2 from dual;
dbms_output.put_line(s1);
dbms_output.put_line(s2);
end;
/
set serverout on
execute foobar;
Hope it helps.
Regards,
Mario Weilguni
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
ports it, but I don't know about other
systems.
http://hpc.uky.edu/cgi-bin/man.cgi?section=all&topic=fgetpos64
Regards,
Mario Weilguni
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(
hen updating/inserting
records only a compatible (a page file with the same number of attributes) page file
is used. Especially master-detail tables would
profit from this, reducing the tuple overhead by another 9%.
Might this be possible?
Regards,
Mario Weilguni
--
Am Freitag, 11. Oktober 2002 14:12 schrieb Tom Lane:
> Mario Weilguni <[EMAIL PROTECTED]> writes:
> > Is it possible to get rid of the "t_natts" fields in the tuple header?
> > Is this field only for "alter table add/drop" support?
>
> "On
scan is possible but not used:
EXPLAIN SELECT * FROM copy_of_forum_list_child WHERE f_id = 1 and
father_name = 'top';
Seq Scan on copy_of_forum_list_child (cost=0.00..2.44 rows=1width=100, costs using
index: 0.00...9.44 rows=... with=...)
Any comments?
Regards,
Mari
ay it's not reproduceable any more. Might this notice indicate a serious
problem?
Best regards,
Mario Weilguni
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregis
quot;IS NULL" should be easy to recognise, since NULL is
very special. This would allow much smaller indices in some applications, for
example I've a case with a table with 20 rows where 4 values (of type
text) are not null. The index size would be much sma
>You can try an index like:
>create index str_idx_url on str(url) where url >= '';
>
>I think that should be identical. ('' is the smallest string, no ?)
Thanks alot, it works now. But I still think the NOT NULL case would be
useful.
B
>I was playing with the Japanese win32 7.2.1 port and I noticed that "select
>0 / 0" caused the server to crash and restart. I understand that it is a
>totally unsupported version, but it should be easy enough to check vs. the
>current version. Note that select 0.0/0.0 worked fine!
Seems to work
he same problem as index usage with/without quotes? However, one
would expect the same output from both queries, either the error message, or
better the 0 rows result.
Regards
Mario Weilguni
---(end of broadcast)---
TIP 3: if posting/rea
ble MySQL 4 not tested?
That's the problem, for every performance test they choose ISAM tables, and
when transactions are mentioned it's said "MySQL has transactions". But why
no benchmarks?
Regards,
Mario Weilguni
---(end of broadcast)---
Postgres 7.1 will be an important milestone.
--
=======
Mario Weilguni KPNQwest Austria GmbH
Senior Engineer Web Solutions Nikolaiplatz 4
tel: +43-316-813824 8020 gr
he total execution time goes down to ~6.5 seconds. That
means that the modified numeric is nearly twice as fast, sure worth
considering that.
--
===
Mario Weilguni KPNQwest Austria GmbH
Senior Engineer Web Solutio
even if shorter than the mask
(Oracle compatible), or raise an error. Currently it gives completly wrong
results, which is the worst option.
I tried to fix this myself, but I'm lost within backend/utils/adt/formatting.c
--
===
Mario Wei
When the mask is not exact, it should raise an error, and not
silently return WRONG values, which is really bad behaviour, and will result
in "lost" data.
--
===
Mario Weilguni KPNQwest Austria GmbH
Senior Engineer Web Solutions Ni
w restoring without
having to set trust in pg_hba.conf. A patch would be simple, in fact I wrote
it within a few minutes.
Or am I completly wrong and there's a better way to accomplish this?
Best regards,
Mario Weilguni
--
==
re could
* eventually fail if the parser cannot identify some way
* how to compare these two types by '='.
* --
*/
Any ideas if this is a bug or simply strict SQL standard?
Best regards,
Mario Weilguni
---
to trigger with more tables. I'll try to create a testcase
and post it.
-Ursprüngliche Nachricht-
Von: Rod Taylor [mailto:[EMAIL PROTECTED]]
Gesendet: Donnerstag, 28. März 2002 16:15
An: Mario Weilguni; Hackers List
Betreff: Re: [HACKERS] deadlock problems with foreign keys
There wa
oming from).
Is there a better way to fix this? Can I post the patch to this list (~150 lines).And
I did not find out how I can detect the large object chunksize, either from getting it
from the headers (include "storage/large_object.h" did not work) or how to get it from
th
hing bad may happen)
I still think that this behaviour is wrong, I asked my collegue to check what
oracle does in this case, it seems that oracle simply makes some sort of
"read lock" on the referenced tables, but no such strong lock as in postgres.
Best regards,
Mario Weilg
able set adatefield=null;
This gets really bad when the actual data is coming from a webinterface, I've
to handle 2 different queries for the case empty string and non-empty string.
Is there a better way to achieve this?
Thanks!
Best regards,
Mario Weilguni
implement such operators (any
example might help)?
Thanks!
Best regards,
Mario Weilguni
Am Sonntag, 4. Februar 2001 20:12 schrieben Sie:
> Mario Weilguni <[EMAIL PROTECTED]> writes:
> > float8 num3 = numeric_float8(num1);
>
> That won't work in the brave new world of 7.1 :-(. You need to do
> something like
>
> float8 num3 =
f postgres documents and still do not
know how to disable autocommit. Is this possible? And how?
Mario Weilguni
--
===
Mario Weilguni KPNQwest Austria GmbH
Senior Engineer Web Solutions
Am Mittwoch, 18. Oktober 2006 13:52 schrieb Andreas Joseph Krogh:
> This has been been discussed before, but Oracle behaves differently, and
> IMHO in a more correct way.
>
> The following query returns NULL in PG:
> SELECT NULL || 'fisk';
>
> But in Oracle, it returns 'fisk':
> SELECT NULL || 'fis
>
>If you want this behaviour you will have to explicitly handle it with
COALESCE().
>
>regards,
>Lukas
True. But there's a point where oracle is really better here, they named
"coalesce" "nvl" => a lot easier to type ;-)
---(end of broadcast)---
TI
Nice, but I still prefer nvl. Coalesce is hard to pronounce, and even harder to
type.
-Ursprüngliche Nachricht-
Von: Andreas Joseph Krogh [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 18. Oktober 2006 15:48
An: pgsql-hackers@postgresql.org
Cc: Mario Weilguni
Betreff: Re: [HACKERS] bug
Yes it's hard for me, maybe because I am no native english speaker.
-Ursprüngliche Nachricht-
Von: Andrew Dunstan [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 18. Oktober 2006 16:11
An: Lukas Kahwe Smith
Cc: Mario Weilguni; pgsql-hackers@postgresql.org
Betreff: Re: [HACKERS] b
> Uh, we did that years ago.
Really?
+ o Add ALTER TABLE RENAME COLUMN (should rename appropriate sequences and
constraints)
Sounds like this is not done, at least not renaming sequencens and constraints,
or am I wrong here?
Regard
Mario Weilguni
-Ursprüngliche Nachri
still is named "foo_bar_seq".
IMO this should do:
Alter sequence foo_bar_seq rename to foo_baf_seq;
Alter table foo alter baf set default nextval('foo_baf_seq')
-Ursprüngliche Nachricht-
Von: Jonah H. Harris [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 17. No
; BEGIN; ...'
> would bypass the check.
Maybe not directly related to that problem, but I had a problem with "-c" last
month, when I noticed that this will not work:
psql -c "set client_encoding=iso-8859-1; select name from customer" (UTF8
database, output
amp, '') should be constant and marked immutable, or am I
wrong here? Or is it not marked immutable because of possible changes on
date_format?
Regards,
Mario Weilguni
---(end of broadcast)---
TIP 3: Have you check
Am Freitag, 12. Januar 2007 14:48 schrieb Martijn van Oosterhout:
> On Fri, Jan 12, 2007 at 11:55:07AM +0100, Mario Weilguni wrote:
> > to_char(timestamp, '') should be constant and marked immutable,
> > or am I wrong here? Or is it not marked immutable because o
same effect on both systems. Because of the large
number of tables involved it's difficult to find a self contained patch, but if
necessary I'll give it a try.
I could give 8.2.3 a try, but I doubt this will help.
Any ideas?
Regards
Mario Weilguni
---(e
Thanks for the info. Is there a fix for 8.1 branch, the production system is
still 8.1.
Regards
Mario Weilguni
Am Donnerstag, 15. Februar 2007 16:25 schrieb Alvaro Herrera:
> Mario Weilguni wrote:
> > Interesting: remove any of the above where conditions solves the problem
&g
his anyway), but I still think this is an
error, making restoration very complicated in such cases...
Or am I doing something completly wrong here?
Best regards,
Mario Weilguni
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner wi
Am Dienstag, 13. März 2007 14:46 schrieb Albe Laurenz:
> Mario Weilguni wrote:
> > Steps to reproduce:
> > create database testdb with encoding='UTF8';
> > \c testdb
> > create table test(x text);
> > insert into test values ('\244'); ==&g
cannot be restored with pg_restore.
A dangerous feature IMO, and will make a lot of DB admins very unhappy if they
have to validate every day if the precious database dumps can be restored in
case of an error.
Best regards,
Mario Weilguni
--
F8? Where
> we had to use iconv?
>
What issues? I've upgraded several 8.0 database to 8.1. without having to use
iconv. Did I miss something?
Regards,
Mario Weilguni
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
wrong encoded sequences (so DBAs still
can turn it on if they really depend on it)?
For me,
Best regards,
Mario Weilguni
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Will this patch make it into 8.2?
http://archives.postgresql.org/pgsql-patches/2004-12/msg00228.php
It's a really nice feature, would be extremly useful with tools like pgpool.
Am Freitag, 7. Juli 2006 19:13 schrieb Bruce Momjian:
> There are roughly three weeks left until the feature freeze on A
bug
fixed in CVS). Problem occurs on a 2 node cluster of 2 Quad-CPU system (Xeon, 2
physical CPU's, 2 hyperthreading), one node running the database, the other one
the webserver.
Any ideas?
Best regards,
Mario Weilguni
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
This works as intended. Try this:
select coalesce(lower(firstname), '') || ' ' || coalesce(lower(lastname), '')
from person
Concating something unknown (=NULL) and a string = unknown (=NULL)
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Andre
What about the "char" type? Isn't it designed for that? Or will this type
disappear in future releases?
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Heikki
Linnakangas
Gesendet: Freitag, 15. September 2006 13:35
An: Martijn van Oosterhout
Cc
Am Dienstag, 19. April 2005 09:18 schrieb Honza Pazdziora:
> Hello,
>
> the nls_string function that makes it possible to sort by arbitrary
> locale has been updated to reflect the changes in error handling in
> PostgreSQL 8.0, due to users using the nls_string sorting on 7.4 and
> requesting it fo
1 - 100 of 143 matches
Mail list logo
