;ll be ready to handle this issue.
Thanks a lot for your help, jeff.
regards
Janning
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Thank you so much for still helping me...
Am 30.03.2012 20:24, schrieb Jeff Davis:
On Fri, 2012-03-30 at 16:02 +0200, Janning Vygen wrote:
The PANIC occurred first on March, 19. My servers uptime ist 56 days, so
about 4th of February. There was no power failure since i started to use
this
Hi,
thanks so much for answering. I found a "segmentation fault" in my logs
so please check below:
> On Tue, 2012-03-27 at 11:47 +0200, Janning Vygen wrote:
>>
>> I am running postgresql-9.1 from debian backport package fsync=on
>> full_page_writes=off
>
&g
ing). Does this error has any relation to this?
Should I check or exchange my hardware? Is it a hardware problem?
Should I still worry about it?
regards
Janning
--
Kicktipp GmbH
Venloer Straße 8, 40477 Düsseldorf
Sitz der Gesellschaft: Düsseldorf
Geschäftsführung: Janning Vygen
Handelsregis
Am 19.03.2012 um 13:22 schrieb Bill Moran :
> In response to Janning Vygen :
>>
>> I am working on postgresql 9.1 and loving it!
>>
>> Sometimes we need a full database dump to test some performance issues
>> with real data.
>>
>> Of course we don
these table columns in my test environment but
instead of real email addresses i want addresses like
random_num...@example.org.
You might be right that it is a good idea to additional encrypt this data.
regards
Janning
Am 19.03.2012 06:24, schrieb Kiriakos Georgiou:
I would store sensitive data
ly reliable way so far. But it is
no fun when dumping and restoring takes an hour.
Does anybody has a better idea how to achieve an anonymized database dump?
regards
Janning
--
Kicktipp GmbH
Venloer Straße 8, 40477 Düsseldorf
Sitz der Gesellschaft: Düsseldorf
Geschäftsführung: Janning Vyge
router between tomcat and DB
server is dropping the connection? I have no clue.
Does anybody know how to fix my problem?
regards
Janning
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
could be smart enough to take a closer
look at the query and optimize its execution plan. If this "problem" is
already known i apologize, but I searched the mailing list and didn't
found any mails regarding this topic. Hard to believe i am the first hit
by this.
kind regards
Janning
On Tuesday 15 June 2010 15:16:19 Ivan Voras wrote:
> On 06/15/10 14:59, Janning wrote:
> > Hi all,
> >
> > as we encountered some limitations of our cheap disk setup, I really
> > would like to see how cheap they are compared to expensive disk setups.
> >
> >
would just like to get a an
idea about how much faster an expensive disk setup could be.
Would it be like 10% faster, 100% or 1000% faster? If you can give me any
hints, I would greatly appreciate it.
kind regards
Janning
--
Sent via pgsql-general mailing list (pgsql-general@postgr
have big advantages and much better performance.
So for further reference for other people reading this thread, I really
recommend trying this out.
best regards
Janning
On Friday 11 June 2010 21:48:54 Martijn van Oosterhout wrote:
> On Thu, Jun 10, 2010 at 04:00:54PM -0400, Greg Smith wrote:
On Thursday 10 June 2010 22:00:54 Greg Smith wrote:
> Janning wrote:
> > 1. With raising checkpoint_timeout, is there any downgrade other than
> > slower after-crash recovery?
>
> Checkpoint spikes happen when too much I/O has been saved up for
> checkpoint time than the s
mum of 61MB dirty
pages.
Your help is very appreciated?
kind regards
Janning
PS: Do I need to post this question on pgsql-perfomance? If so, please let me
know.
On Wednesday 09 June 2010 18:53:23 Janning wrote:
> Hi,
>
> we currently encounter an increasing load on our websi
meout.
do you have any hints for us how to tune our configuration to avoid spikes?
kind regards
Janning
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Hi,
I am using prepared statements in Postgresql 8.4.
Does Postgresql
a) plans statements only once when PREPARE is called?
b) replans statements from time to time
c) replans when underlying statistics change on behalf of ANALYZE command?
kind regards
Janning
--
http://www.kicktipp.de
wrong plan (like sequence scan instead of using an index)
But I remember a post of tom lane who said that prepared statements get
replaned since 8.4 if underlying statistics change. But I really can't find it.
Maybe I do not remember correctly.
kind regards
Janning
> --
> Joshua Tolley / eggyknap
> End Point Corporation
> http://www.endpoint.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
o this question, where you can find an
excellent answer, too:
http://stackoverflow.com/questions/2920740/should-i-activate-c3p0-statement-
pooling/2921340#2921340
kind regards
Janning
http://www.kicktipp.de/
>
> --
> Joshua Tolley / eggyknap
> End Point Corporation
> http://www.endpoint.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Does PG replans prepared statements from time
to time if underlying data statistics change?
I am glad if you help me and give me some insights to managing my connection
pool the right way.
kind regards
Janning
PS: I think its ok to post this on general and not on pgsql-jdbc as I am not
subcrib
n just for this row (or maybe for a bunch of
rows on the same page). if it comes to updating the next row it happens again.
re-checking 4+ rows with a very expensive sub-select plan is not good at
all. 4 times 800 ms = 10 hours.
Am I right with my suspicion?
If yes, how ca
On Tuesday 21 July 2009 18:09:57 you wrote:
> Janning Vygen writes:
> > On Tuesday 21 July 2009 15:49:36 Tom Lane wrote:
> >> Well, you could turn it off during the peak times.
> >
> > It affords a server restart which is not a good idea.
>
> Changing loggi
On Tuesday 21 July 2009 15:49:36 Tom Lane wrote:
> Janning Vygen writes:
> > On Monday 20 July 2009 19:24:13 Bill Moran wrote:
> >> Have you benchmarked the load it creates under your workload?
> >
> > Yes, it takes up to 15% of our workload in an average use ca
nted soon, it wouldn't help
me. As i need to analyze my load now!
kind regards
Janning
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
onal disks for logging. In this scenario you just can't log
everything. log_min_duration gives you only a view to long running queries but
that is just on half of the whole picture.
kind regards
Janning
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make cha
hi,
thanks for your comments on this.
On Thursday 16 July 2009 15:05:58 you wrote:
> In response to Janning Vygen :
> > hi,
> >
> > http://archives.postgresql.org/pgsql-general/2009-03/msg00581.php
> >
> > This was my suggestion about introducing a statment to g
hi,
http://archives.postgresql.org/pgsql-general/2009-03/msg00581.php
This was my suggestion about introducing a statment to get a sample of SQL
statements. Nobody answered yet. Why not? i think my suggestion would help a
lot. Or was it kind of stupid?
kind regards
Janning
--
Sent via
On Wednesday 15 April 2009 19:21:03 you wrote:
> Janning Vygen writes:
> > Now i see that the errors occur _exactly_ every 4000 seconds (1 hour, 6
> > minutes and 40 seconds). I have no clue as i only have one cronjob at
> > night concerning postgresql. I have no autovacuum
Hi,
Thank you for this great and ultra-fast support! One more question:
On Wednesday 15 April 2009 17:38:51 you wrote:
> Janning Vygen writes:
> > I am investigating some error messages in my log file:
> >
> > Apr 15 08:04:34 postgres[20686]: [4-1] 2009-04-15 08:04:34 CE
ce. Can someone give me a
hint what characters in which encoding those bytes might be?
kind regards
Janning
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Monday 16 March 2009 15:13:51 Scott Marlowe wrote:
> On Mon, Mar 16, 2009 at 7:15 AM, Janning Vygen wrote:
> > Hi,
> >
> > Why does default_statistic_target defaults to 10?
> >
> > I suggest to setting it to 100 by default:
>
> Already done in 8.4
GREA
their system in every possible way.
- no problems for growing databases with unequal distributed data
But maybe there are some other reasons not setting it to a higher value. If
so, please tell me.
kind regards
Janning
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make ch
in the log with a reasonable log_min_duration setting.
With my proposal every 100th query is logged and you get a detailed view of
your database usage without excessive disk IO. Of course it should be
combinable with log_min_duration.
What do you think about it?
kind regards
Janning
--
automatic security updates coming with debian out of the box. I have to look
for another way to replan. Maybe i just have to close and reopen my
connections from time to time.
kind regards
Janning
---(end of broadcast)---
TIP 1: if posting/readin
range to me too, but i never had foreign keys to the same table.
it works if you define your chekced_by FK deferrable with
checked_by INT REFERENCES users (id) ON UPDATE CASCADE ON DELETE SET NULL
DEFERRABLE INITIALLY DEFERRED,
it seams that postgresql does its job in a procedural way instead of
relational.
kind regards,
Janning
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
ler, etc as well.
no, it was different hardware and maybe different compiler. Hmm, i do
understand why computers are not masters of floating point (though i dont
understand how they can fly air planes) , but a dump should be something
which can be used across different hardware, shouldn't it?
k
it in
section "data types" without saying how much speed-up i gain. Please, i just
want to know if its worth it. Is it more like 0,1%, 1%, 10% or 50%?
any help on speeding this up is very appreciated.
kind regards,
janning
---(end of
Thanks for your fast reply.
Am Mittwoch, 12. April 2006 18:31 schrieb Merlin Moncure:
> On 4/12/06, Janning Vygen <[EMAIL PROTECTED]> wrote:
> > Hi,
> > disk 1: OS, tablespace
> > disk 2: indices, WAL, Logfiles
> > - Does my partitioning make sense?
>
> w
ts one of those
controllers which sucks.
kind regards,
janning
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
if you dont have those update SQL scripts it can become quite difficult. You
have to compare original schema and current schema. To get a schema look at
pg_dump option '-s'. Compare those schemas and write your update SQL scripts.
kind regards
janning
---(end of
Am Montag, 23. Januar 2006 21:57 schrieb Tom Lane:
> Janning Vygen <[EMAIL PROTECTED]> writes:
> > ok, shouldn't i upgrade to 8.1 instead of 8.0.6 if i can?
>
> Up to you --- you have more risk of compatibility issues if you do that,
> whereas within-branch update
TOM! Ich will ein Kind von Dir!!
(it means 'something like': thank you so much. you just saved my life!)
Am Montag, 23. Januar 2006 21:16 schrieb Tom Lane:
> Janning Vygen <[EMAIL PROTECTED]> writes:
> >> OK, what's the schema of this tabl
Am Montag, 23. Januar 2006 20:30 schrieb Tom Lane:
> Janning Vygen <[EMAIL PROTECTED]> writes:
> > Ok, i got the reffilnode from pg_class and compiled pg_filedump. result
> > of ./pg_filedump -i -f -R 3397
> > /home/postgres8/data/base/12934120/12934361 > filedump.
Am Montag, 23. Januar 2006 17:05 schrieb Tom Lane:
> Janning Vygen <[EMAIL PROTECTED]> writes:
> > pg_dump: ERROR: invalid memory alloc request size 18446744073709551614
> > pg_dump: SQL command to dump the contents of table "spieletipps" failed:
> > PQendcopy
m
company selling things i could need.
If there is someone nearby who might help, please answer via personal E-Mail
([EMAIL PROTECTED]). I guess we could meet very for a few hours and we will
see if further consultancy is needed.
kind regards,
janning
[*] which i not named to get not listed in
et wurde.
Die Verbindung zum Server wurde verloren. Versuche Reset: Fehlgeschlagen.
(it means: server closed the connection unexpectedly. ... Try to reset
connection failed.)
Please help me!
kind regards,
janning
---(end of broadcast)---
TIP 3: Hav
are usually much more efficient
than triggers. And they are much more relational in my opinion.
kind regards,
janning
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
Am Donnerstag, 20. Oktober 2005 19:59 schrieb David Fetter:
> On Thu, Oct 20, 2005 at 06:04:53PM +0200, Janning Vygen wrote:
> > By the way: What i really miss is a troubleshooting document in the
> > docs.
> > > That's a great idea. Please post a doc patch with some
Am Donnerstag, 20. Oktober 2005 16:04 schrieb Tom Lane:
> Janning Vygen <[EMAIL PROTECTED]> writes:
> > it says:
> > $ export PGOPTIONS="-P"
> > $ psql broken_db
> >
> > It should be:
> > $ export PGOPTIONS="-P"
>
dexes in a particular database,
without trusting them to be valid already:
$ export PGOPTIONS="-P"
$ postgres broken_db
,shouldn't it?
kind regards,
janning
---(end of broadcast)---
TIP 5: don't forget t
arises again.
kind regards,
janning
Am Mittwoch, 28. September 2005 16:07 schrieb Tom Lane:
> Janning Vygen <[EMAIL PROTECTED]> writes:
> > I recently reported this problem and i would like to help solving it. But
> > how can i build a self-contained test-case? It just happens som
le in pg_type.
Then i run something like
for I in 1..20 do
DROP TYPE pg_temp_$I.spiele;
DROP TYPE pg_temp_$I.temp_gc;
done;
After this everything works fine again.
kind regards,
Janning Vygen
---(end of broadcast)---
TIP 1: if posting/reading
rd the time for rewriting the
app to not use temp tables. So i need to fix it. any help is very
appreciated.
kind regards,
janning
---(end of broadcast)---
TIP 6: explain analyze is your friend
Am Donnerstag, 15. September 2005 15:31 schrieb Tom Lane:
> Janning Vygen <[EMAIL PROTECTED]> writes:
> > $ DROP TYPE temp_gc;
> > ERROR: type "temp_gc" does not exist
>
> The temp schema is evidently not in your search path. You need
> something li
> Janning Vygen writes:
> > Am Samstag, 10. September 2005 18:05 schrieb Tom Lane:
> >> If there's no pg_depend entry then DROP TYPE should work. Otherwise
> >> you might have to resort to manually DELETEing the pg_type row.
>
> > Thanks for your det
Am Samstag, 10. September 2005 18:05 schrieb Tom Lane:
> Janning Vygen <[EMAIL PROTECTED]> writes:
> > i guess the table was dropped but not the corresponding type.
> > How can things like this happen?
>
> Corrupted pg_depend table maybe? You might try REINDEXing pg
| f | 0 |
-1 |0 | |
(1 row)
i guess the table was dropped but not the corresponding type.
How can things like this happen?
How can i fix it? Can i just drop the type from pg_type?
kind regards,
janning
--
and rules if you have
update and insert statemnts which affect only a few rows. but if it comes to
affecting many rows, you should use rules. But rules are more difficult to
understand.
kind regards,
janning
---(end of broadcast)---
TIP
Am Mittwoch, 27. Juli 2005 09:47 schrieb Philippe Lang:
> Thanks Tom, thanks Janning,
>
> I found triggers very convenient to do different tasks in the database, and
> these tasks go far beyond what we can do in rules, Janning.
Right. There are some things that can't be done wit
are really doing i can help you.
as your mail is .ch you might prefer german language and can contact via
personal mail.
kind regards,
janning
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
d lately?
- another parameter to look at is random_page_cost: "Sets the planner's
estimate of the cost of a nonsequentially fetched disk page. This is measured
as a multiple of the cost of a sequential page fetch. A higher value makes it
more likely a sequential scan will be used, a lower value makes it more
likely an index scan will be used. The default is four."
kind regards,
janning
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Am Dienstag, 19. Juli 2005 15:40 schrieb Tom Lane:
> Janning Vygen <[EMAIL PROTECTED]> writes:
> > On more related question:
> > I updated pg_trigger and pg_constraint and changed all my FK:
> >
> > UPDATE pg_trigger
> > SET
> > tgdeferrable
[sorry for resending again. i am not at my usual desktop at the moment and
used the wrong sender address]
Am Dienstag, 19. Juli 2005 15:40 schrieb Tom Lane:
> Janning Vygen <[EMAIL PROTECTED]> writes:
> > On more related question:
> > I updated pg_trigger and pg_constraint
sql. If i can help any further with a complete example,
please let me know.
On more related question:
I updated pg_trigger and pg_constraint and changed all my FK:
UPDATE pg_trigger
SET
tgdeferrable = true,
tginitdeferred = true
WHERE tgconstrname LIKE 'fk_%'
;
UPDATE pg_constraint
SET
condeferrable = true,
condeferred = true
WHERE conname LIKE 'fk_%'
;
did i make it right this time updating the pg_catalog? Or is there more to do
in pg_catalog?
kind regards
janning
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
is mostly correct and maybe it helps
you improving postgresql. If i can help any further with a complete example,
please let me know.
On more related question:
I updated pg_trigger and pg_constraint and changed all my FK:
UPDATE pg_trigger
SET
tgdeferrable = true,
Am Montag, 18. Juli 2005 16:56 schrieb Tom Lane:
> Janning Vygen <[EMAIL PROTECTED]> writes:
> > But why doesn't it work if i make alle FK deferrable initially deferred?
>
> You didn't do it right --- I don't believe the code actually looks at
> pg_constrai
Am Montag, 18. Juli 2005 16:28 schrieb Stephan Szabo:
> On Mon, 18 Jul 2005, Tom Lane wrote:
> > Janning Vygen <[EMAIL PROTECTED]> writes:
> > > I have lots of tables with mutli-column PK and multi-column FK. All FK
> > > are cascading, so updating a PK
#x27;;
Is it all what needs to be done to pg_catalog? Or did i miss something. But to
me it looks ok as a table description with '\d' actually states "deferrable
initially deferred" for all my FK.
But with all FK deferred i still get the error above. If i drop a few FK
completely to avoid a circular roundtrip everything works fine (but of course
this is not an option as i need these FKs)
Any help is very appreciated.
kind regards,
janning
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Am Freitag, 15. Juli 2005 19:19 schrieb Tom Lane:
> Janning Vygen <[EMAIL PROTECTED]> writes:
> > How can a function determine in which isolation level it runs?
>
> select current_setting('transaction_isolation');
Thank you for the hint.
I didn't find it m
zable transaction, but to be sure that my materialized view is
consistent with the rest of the data i would like to enforce it.
Is it possible to get info about the current transaction isolation level?
kind regards,
janning
---(end of broa
Am Mittwoch, 13. Juli 2005 15:35 schrieb Tom Lane:
> Janning Vygen <[EMAIL PROTECTED]> writes:
> > this way it works:
> >
> > CREATE TEMP TABLE ranking AS *Q*;
> > EXECUTE 'UPDATE temp_gc SET gc_rank = ranking.rank
> > FROM ranking WHERE temp_gc.mg_name
Am Mittwoch, 13. Juli 2005 16:04 schrieb Tom Lane:
> Janning Vygen <[EMAIL PROTECTED]> writes:
> > I was just testing some configuration settings, especially increasing
> > shared_buffers and setting fsync to false. And suddenly it happens 3
> > times out of ten that
Hi,
Am Mittwoch, 13. Juli 2005 00:03 schrieb Tom Lane:
> Janning Vygen <[EMAIL PROTECTED]> writes:
> > I have a guess, what happens here: The order of the subselect statement
> > is dropped by the optimizer because the optimizer doesn't see the
> > "side-effe
e been deleted in a single transaction."
I was just testing some configuration settings, especially increasing
shared_buffers and setting fsync to false. And suddenly it happens 3 times
out of ten that i get this error.
It seems to me that setting fsync to false was not a good ide
here: The order of the subselect statement is
dropped by the optimizer because the optimizer doesn't see the "side-effect"
of the ranking function. that's ok because using such functions isn't SQLish,
i guess.
Is there a way to FORCE the optimizer to keep things orders li
() sometimes being greater
than 1, which should not occur. Please use a
CASE WHEN sin(...) > 1 THEN 1 ELSE sin(...) END
if you have the same problem.
kind regards,
janning
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
your other rule is trying to insert nothing like the UPDATE command
in the example above.
kind regards,
janning
---(end of broadcast)---
TIP 8: explain analyze is your friend
ll be...
I guess i will use one sequence for all tables if there are now drawbacks.
BTW: OIDs are using the same conecpt, don't they? And for me it makes sense
to use a sequence only for getting a unique identifier and nothing else. even
better if this identifier is unique among all tables.
Than
sequence for all tables?
kind regards,
janning
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
you could delete all data files anyway which would be much more
serious than adding or deleting users.!?
Did anybody tried something like this before? Does it make sense?
kind regards,
janning
---(end of broadcast)---
TIP 4: Don't 'ki
%\342\343\317\323\015\01220 0 obj\015<< \015/Linearized 1
\015/O 22 \015/H [ 660 209 ] \..."
how can things like this happen? Is it a problem with COPY command?
I guess my input into bytea must be ok otherwise postgresql should report an
error on insert statmenet, shouldn't it?
Am Montag, 4. April 2005 17:36 schrieb Tom Lane:
> Janning Vygen <[EMAIL PROTECTED]> writes:
> > i have a databse in postgresql 7.4 with some pdf files in a bytea column.
> >
> > everything works fine but sometimes when i dump and restore i get
> >
> > psql:
%\342\343\317\323\015\01220 0 obj\015<< \015/Linearized 1
\015/O 22 \015/H [ 660 209 ] \..."
how can things like this happen? Is it a problem with COPY command?
I guess my input into bytea must be ok otherwise postgresql should report an
error on insert statmenet, shouldn't it?
Am Dienstag, 29. März 2005 16:37 schrieb Tom Lane:
> Janning Vygen <[EMAIL PROTECTED]> writes:
> > Am Montag, 28. März 2005 18:06 schrieb Tom Lane:
> >> The only way for pg_xlog to bloat vastly beyond what it's supposed to be
> >> (which is to say, about twic
Am Montag, 28. März 2005 18:06 schrieb Tom Lane:
> "Janning Vygen" <[EMAIL PROTECTED]> writes:
> > My disk was running full with 100 GB (!) of data/pg_xlog/ files.
>
> The only way for pg_xlog to bloat vastly beyond what it's supposed to be
> (which is to sa
Am Montag, 28. März 2005 13:46 schrieb Gustavo Franklin Nóbrega - Planae:
> Hi Janning!
>
> You need to expand your pg_xlog partition. If you use reiserfs, you can
> do this with resize_reiserfs. If you use ext2/ext3 you may try reise2fs.
This is not an option to me at the moment
ont know much of all the
underlying storage, WAL and xlog things. Maybe i could just delete all files
in this directory?
Can anybody give me some hints what to do or how to ask?
i am really desperate at the moment.
kind regards,
Janning
please excuse bad english and typos. i am kind of n
or mean. I didn't found anything in the archives (searched
google with 'pg_restore "incorrect data check"'). Just one unanswered message
( http://archives.postgresql.org/pgsql-general/2003-08/msg01035.php )
kind regards,
janning
--
PLANWERK 6 websolutions
Herzogstraße 85,
or mean. I didn't found anything in the archives (searched
google with 'pg_restore "incorrect data check"'). Just one unanswered message
( http://archives.postgresql.org/pgsql-general/2003-08/msg01035.php )
kind regards,
janning
---(end of broadcast)---
pg_restore be made to ignore the error?
>
> It does, at least since 8.0.
I guess, it's time to upgrade!
kind regards,
Janning
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
contains CREATE LANGUAGE statements. They are
not needed if template1 contains the language, right?
I didnt found anythng in the archives even though i am sure not to be the
first one having this problem.
kind regards,
janning
here is what i did with 7.4.6:
+++ AS DB SUPERUSER
# createlang
contains CREATE LANGUAGE statements. They are
not needed if template1 contains the language, right?
I didnt found anythng in the archives even though i am sure not to be the
first one having this problem.
kind regards,
janning
here is what i did with 7.4.6:
+++ AS DB SUPERUSER
# createlang
n adresses multiple
times and get the right data with COALESCE function which returns the first
value which is NOT NULL.
If you still have difficulties, please send your schema.
kind regards,
janning
---(end of broadcast)---
TIP 3: if posting/read
FROM file_info_1 a
WHERE a.file_name='/'
UNION
SELECT b.file_name
FROM file_info_2 b
WHERE b.file_name='/'
UNION
SELECT c.file_name
FROM file_info_3 c
WHERE c.file_name='/'
ORDER BY 1;
for further documentation visit
http://w
Am Montag, 13. Dezember 2004 17:37 schrieb Bruno Wolff III:
> On Mon, Dec 13, 2004 at 10:58:25 +0100,
>
> Janning Vygen <[EMAIL PROTECTED]> wrote:
> > Am Samstag, 11. Dezember 2004 20:06 schrieb Bruno Wolff III:
> >
> > maybe your are right. But with Sequence
Am Samstag, 11. Dezember 2004 20:06 schrieb Bruno Wolff III:
> On Thu, Dec 09, 2004 at 18:32:19 +0100,
>
> Janning Vygen <[EMAIL PROTECTED]> wrote:
> > "id" should be positive
> > "id" should not have gaps within the same account
> > "
s it would
be nice if he/she is willing to sahre the code with me.
- did anyone implemented a table like this and came to the conclusion that
this shouldn't be done for any reasons out of my sight? (i don't bother about
updating a primary key)
kind regards,
janning
-
Am Dienstag, 16. November 2004 16:39 schrieb Doug McNaught:
> Janning Vygen <[EMAIL PROTECTED]> writes:
> > So how do i easily empty all page/file caches on linux (2.4.24)?
>
> Probably the closest you can easily get is to put the Postgres data
> files on their own partit
und what i need. (of course i searched the
archives, too)
So how do i easily empty all page/file caches on linux (2.4.24)?
Sorry for beeing a little bit OT, but i think my question still relates to
postgresql.
kind regards,
janning
---(end of broadcast)-
h seems to have the same meaning (some value which
is compared to another value of little_table).
why dont you put just one column "y" in your big_table?
kind regards,
janning
> Mike Mascari
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
nd regards,
janning
---(end of broadcast)---
TIP 8: explain analyze is your friend
1 - 100 of 123 matches
Mail list logo
