On Sat, Dec 19, 2015, 01:50 Andrew Dunstan <and...@dunslane.net> wrote:
>
>
>
>
> On 12/18/2015 05:18 PM, Gaetano Mendola wrote:
> > From documentation about "CREATE DATABASE name WITH TABLESAPCE =
> > tablespace_name":
> >
&
X/PG_9.4_201409291/80335/80336
/home/kalman/tablespace_XXX/PG_9.4_201409291/80335/80336: empty
as you can see the CREATE DATABASE documentation is honored but the system
is failing to give me the right tablespace location for that table.
Regards
On Thu, 17 Dec 2015 at 15:36 Tom Lane <t...@
On Thu, 17 Dec 2015 at 15:36 Tom Lane <t...@sss.pgh.pa.us> wrote:
> Gaetano Mendola <mend...@gmail.com> writes:
> > I'm playing around with tablespace (postgresq 9.4) and I found out what I
> > believe is a bug in pg_tables.
> > Basically if you create a databas
I'm playing around with tablespace (postgresq 9.4) and I found out what I
believe is a bug in pg_tables.
Basically if you create a database in a table space X and then you create a
table on the database the table is created correctly on the tablespace X (
I did a check on the filesystem) however
If the compiler is good the assignment is elided indeed, that's not what I
meant to point out.
On Thu, 28 May 2015 at 22:17 Andres Freund and...@anarazel.de wrote:
On 2015-05-28 20:14:33 +, Gaetano Mendola wrote:
src/backend/commands/explain.c:1692
src/backend/commands/explain.c:1874
Hi,
in the following spots:
src/backend/commands/explain.c:1692
src/backend/commands/explain.c:1874
src/backend/commands/explain.c:1986
there is the following assignment:
ancestors = list_delete_first(ancestors);
but it has no effect at all being that a function parameter and not used
While at it the assert(cnfa != NULL cnfa-nstates != 0); at
src/backend/regex/rege_dfa.c:282
is issued too late indeed at line 278 and 279 cnfa was already
dereferenced.
Same for assert(t != NULL) in src/backend/regex/regexec.c:821 is issued way
too late.
On Thu, 28 May 2015 at 15:59 Tom
I'm playing with a static analyzer and it's giving out some real error
analyzing postgresql code base like the following one
src/backend/access/transam/commit_ts.c
return *ts != 0 // line 321
but a few line up (line 315) ts is checked for null, so either is not
needed to check for null or *ts
At line 650 I can read:
if ((leaf-lsize - segsize) - (leaf-lsize - segsize) BLCKSZ / 4)
break;
I believe one of the two should be leaf-rsize
--
cpp-today.blogspot.com
I have read Peter Eisentraut blog entry about Moving to C++, I full agree
with him about what he wrote.
Is there any interest or work in progress in making the entire Postgresql
code
base compilable by a C++ compiler?
Regards
Gaetano Mendola
--
cpp-today.blogspot.com
Reading this mailing list via newsgroup (news.postgresql.org port
119) I can see that last legitimate message is from
29 August since then only RUSSIAN posts are present.
Regards
Gaetano Mendola
--
cpp-today.blogspot.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
May be someone of you is interested in this
ADBIS workshop on GPUs in Databases
http://gid2012.cs.put.poznan.pl/
Regards
Gaetano Mendola
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
Hi all,
Is the following code well formed?
oldContext = MemoryContextSwitchTo(newContext);
if (something_bad) {
elog(ERROR, ...);
}
...
MemoryContextSwitchTo(oldContext);
or do I have to ripristinate the oldContext before to issue the elog ?
Regards
Gaetano Mendola
--
Sent via
value or on certain element size).
Regards
Gaetano Mendola
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
value or on certain element size).
Regards
Gaetano Mendola
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
that did come in my mind.
What do you mean with you could introduce some kind of parallelism?
As far as I know any algorithm using the divide and conquer can be
parallelized.
Regards
Gaetano Mendola
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
that did come in my mind.
What do you mean with you could introduce some kind of parallelism?
As far as I know any algorithm using the divide and conquer can be
parallelized.
Regards
Gaetano Mendola
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
On 13/02/2012 08:26, Greg Smith wrote:
On 02/11/2012 08:14 PM, Gaetano Mendola wrote:
The trend is to have server capable of running CUDA providing GPU via
external hardware (PCI Express interface with PCI Express switches),
look for example at PowerEdge C410x PCIe Expansion Chassis from DELL
On Feb 13, 2012 11:39 a.m., Kohei KaiGai kai...@kaigai.gr.jp wrote:
2012/2/13 Greg Smith g...@2ndquadrant.com:
On 02/11/2012 08:14 PM, Gaetano Mendola wrote:
The trend is to have server capable of running CUDA providing GPU via
external hardware (PCI Express interface with PCI Express
On Feb 13, 2012 7:49 p.m., Greg Stark st...@mit.edu wrote:
I don't think we should be looking at either CUDA or OpenCL directly.
We should be looking for a generic library that can target either and
is well maintained and actively developed. Any GPU code we write
ourselves would rapidly be
/CUDALibraries/doc/NPP_Library.pdf
(take a look at around page 620).
Regards
Gaetano Mendola
Oleg
On Sun, 12 Feb 2012, Gaetano Mendola wrote:
On 19/09/2011 16:36, Greg Smith wrote:
On 09/19/2011 10:12 AM, Greg Stark wrote:
With the GPU I'm curious to see how well
it handles multiple processes
.
So compared with pg_qsort thrust::sort gives you the same flexibility.
http://docs.thrust.googlecode.com/hg/group__sorting.html
Regards
Gaetano Mendola
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
, 1943
Regards
Gaetano Mendola
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
I wonder if somewhere in Postgres source we are relying on the GCC
correct behaviour regarding the read-modify-write of bitfield in
structures.
Take a read at this https://lwn.net/Articles/478657/
sorry if this was already mentioned.
Regards
Gaetano Mendola
--
Sent via pgsql-hackers mailing
with this one?
Regards
Gaetano Mendola
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Fri, Jun 20, 2008 at 4:37 PM, Tom Lane [EMAIL PROTECTED] wrote:
Gaetano Mendola [EMAIL PROTECTED] writes:
we have faced lately dumps not valid, the bug can be replicated using a
8.2.9 or
a 8.3.1 server.
These are the steps to create the database that will generate a not valid
dump
Hi all,
we have faced lately dumps not valid, the bug can be replicated using a 8.2.9 or
a 8.3.1 server.
These are the steps to create the database that will generate a not valid dump:
---
CREATE TABLE t_public (
a integer
);
CREATE OR
Tom Lane wrote:
Gaetano Mendola [EMAIL PROTECTED] writes:
since long time I have implemented a materialized view, today I had to add a
new field and I faced the following (I believe) bug.
The bug can be replicated on a 8.2.7
Cached plan for the function's UPDATE. Should work okay in 8.3
Hi all,
since long time I have implemented a materialized view, today I had to add a
new field and I faced the following (I believe) bug.
The bug can be replicated on a 8.2.7
-- SETUP
create table test (a integer, b integer);
create table test_trigger (a integer);
CREATE OR REPLACE FUNCTION
was able to fix it in the following mode:
status)
# status -p /var/run/postmaster.${PGPORT}.pid
status postmaster
script_result=$?
;;
Commented the original line and replaced with the one just below.
Regards
Gaetano Mendola
--
Sent via pgsql-hackers mailing list
Gaetano Mendola
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHov3I7UpzwH2SGd4RApR+AJ0dG/+0MoB3PMD1kRgQt0BisHwQBACgzVwC
BN/SBWrvVxVE9eBLK0C1Pnw=
=9Ucp
-END PGP SIGNATURE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn van Oosterhout wrote:
On Fri, Feb 01, 2008 at 12:08:56PM +0100, Gaetano Mendola wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I'm using 8.2.6 and I'm observing a trange behaviour using
offset and limits.
Please post
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gregory Stark wrote:
Gaetano Mendola [EMAIL PROTECTED] writes:
I don't get why a limit is going to change the query plan and most of all
decreasing
the performances.
Until we see the explain analyze it won't be clear what exactly is going
: ((_to = 1500) AND (_from = 1550))
Total runtime: 0.700 ms
(8 rows)
Regards
Gaetano Mendola
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHo1SB7UpzwH2SGd4RAhTeAJ0WL49jjUgCWSrNopV/8L+rbOLaEgCfTDlh
7.943239358636 6078 total
real0m16.313s
user0m1.428s
sys 0m3.802s
so instead of 32 or such rename it did the rename 3K times.
To solve the problem is it possible to kill that process? (will it be
respawned?)
Regards
Gaetano Mendola
-BEGIN PGP
hubert depesz lubaczewski wrote:
On Mon, Oct 29, 2007 at 09:52:24AM +0100, Gaetano Mendola wrote:
it seems that the stats collector on my box is using more CPU than
it did in the past.
it's well known bug, and it was fixed in 8.2.4:
http://www.postgresql.org/docs/current/interactive
hubert depesz lubaczewski wrote:
On Mon, Oct 29, 2007 at 09:52:24AM +0100, Gaetano Mendola wrote:
it seems that the stats collector on my box is using more CPU than
it did in the past.
it's well known bug, and it was fixed in 8.2.4:
http://www.postgresql.org/docs/current/interactive/release
Andrew Dunstan wrote:
Gaetano Mendola wrote:
hubert depesz lubaczewski wrote:
On Mon, Oct 29, 2007 at 09:52:24AM +0100, Gaetano Mendola wrote:
it seems that the stats collector on my box is using more CPU than
it did in the past.
it's well known bug
Magnus Hagander wrote:
Gaetano Mendola wrote:
hubert depesz lubaczewski wrote:
On Mon, Oct 29, 2007 at 09:52:24AM +0100, Gaetano Mendola wrote:
it seems that the stats collector on my box is using more CPU than
it did in the past.
it's well known bug, and it was fixed in 8.2.4:
http
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I'm observing that is not allowed to LOCK a table in a
STABLE/IMMUTABLE function but at same time is allowed
a SELECT FOR UPDATE.
Is that normal?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with
Tom Lane wrote:
Gaetano Mendola [EMAIL PROTECTED] writes:
I'm observing that is not allowed to LOCK a table in a
STABLE/IMMUTABLE function but at same time is allowed
a SELECT FOR UPDATE.
Really? AFAICS, CommandIsReadOnly() will reject SELECT FOR UPDATE too.
kalman=# select version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom Lane wrote:
Gaetano Mendola [EMAIL PROTECTED] writes:
I can immagine a case when a lower module exports a view to upper layer
stating
the interface as list of fields:
first_name, last_name,
with an *hidden* field that is a function
-
PostgreSQL 8.2.3 on i686-redhat-linux-gnu, compiled by GCC gcc (GCC) 4.1.1
20070105 (Red Hat 4.1.1-51)
(1 row)
Regards
Gaetano Mendola
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFF+V2
update_test where c =
'foo')
WHERE a = 10;
What's the expected result if the tuple from subselect is more than 1?
I expect no update at all in case of void result set, is this the case ?
Regards
Gaetano Mendola
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gaetano Mendola wrote:
Tom Lane wrote:
Gaetano Mendola [EMAIL PROTECTED] writes:
[ 8.2 evaluates volatile functions in the targetlist of a view ]
If I mark the function as STABLE or IMMUTABLE then even with version
8.2 the function
Martijn van Oosterhout wrote:
On Fri, Mar 09, 2007 at 10:59:56AM +0100, Gaetano Mendola wrote:
Is really this what we want? I did a migration 8.0.x = 8.2.3 and I had on
first hour of service up
lot of queries blocked due to this, consider in my case I have on v_ta
milions of records
Florian G. Pflug wrote:
Gaetano Mendola wrote:
Martijn van Oosterhout wrote:
On Fri, Mar 09, 2007 at 10:59:56AM +0100, Gaetano Mendola wrote:
Is really this what we want? I did a migration 8.0.x = 8.2.3 and I
had on first hour of service up
lot of queries blocked due to this, consider in my
Florian G. Pflug wrote:
Martijn van Oosterhout wrote:
On Fri, Mar 09, 2007 at 10:59:56AM +0100, Gaetano Mendola wrote:
Is really this what we want? I did a migration 8.0.x = 8.2.3 and I
had on first hour of service up
lot of queries blocked due to this, consider in my case I have on
v_ta
Tom Lane wrote:
Gaetano Mendola [EMAIL PROTECTED] writes:
[ 8.2 evaluates volatile functions in the targetlist of a view ]
If I mark the function as STABLE or IMMUTABLE then even with version
8.2 the function is not evaluated. Is this the intended behavior?
Yes; people complained that we
is not evaluated in case of select a from
v_test.
If I mark the function as STABLE or IMMUTABLE then even with version 8.2 the
function
is not evaluated. Is this the intended behavior? I didn't see something about
it in
the release note.
Regards
Gaetano Mendola
-BEGIN PGP SIGNATURE
Tom Lane wrote:
Could you get a gdb stack trace from that crash? If the buildfarm
run is under a suitable ulimit, it should be leaving a core file
in the test PGDATA directory.
Unfortunately the core size for the user pgfarm is 0:
$ulimit -c
0
However I did a configure, make and make check
printf(OK\n);
return 0;
}
$ gcc -D_GNU_SOURCE tom.c -o tom
$ ./tom
failed: Success
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
... no
checking for openssl/ssl.h... no
configure: error: header file openssl/ssl.h is required for OpenSSL
error: Bad exit status from /var/tmp/rpm-tmp.3109 (%build)
actually I have that file:
# locate openssl/ssl.h
/usr/include/openssl/ssl.h
Can someone help me in this ?
Regards
Gaetano Mendola
Hi all,
I installed postgres 8.0.4 on a win32 box and I found out:
libpq-fe.h and libpqdll.lib are missing.
Is that normal?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 6: explain analyze is your friend
: (sp_connected_test(id_user) = false)
(7 rows)
Is not possible in any way push postgres to apply that function to the right
table ?
Shall I rewrite the views figuring out wich column is better to expose ?
Regards
Gaetano Mendola
---(end of broadcast
Tom Lane wrote:
Gaetano Mendola [EMAIL PROTECTED] writes:
CREATE OR REPLACE VIEW v_current_connection AS
SELECT ul.id_user
FROM user_login ul,
current_connection cc
WHERE ul.id_user = cc.id_user;
# explain select * from v_current_connection_test where
sp_connected_test(id_user
Rod Taylor wrote:
I have maintenace_work_mem set to about 1GB in size.
Isn't a bit too much ?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command
work_around the problem rewriting the view:
CREATE VIEW v_current_connection_test
AS SELECT cc.id_user, cc.connected
FROM current_connection cc,
user_login ul
WHERE cc.id_user = ul.id_user AND
connected = TRUE;
Regards
Gaetano Mendola
---(end
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom Lane wrote:
Gaetano Mendola [EMAIL PROTECTED] writes:
What I'm experiencing is a problem ( I upgraded today from
7.4.x to 8.0.3 ) that I explain here:
The following function just return how many records there
are inside the view
Hi all,
I'm the administrator of that machine and PLCheck is failing.
Is there anything I can do to fix it ?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 6: explain analyze is your friend
Tom Lane wrote:
Gaetano Mendola [EMAIL PROTECTED] writes:
I'm the administrator of that machine and PLCheck is failing.
Is there anything I can do to fix it ?
What version of Python have you got on that thing? It seems to be
emitting still another spelling of the encoding error message
to a replayng engine
to perform ( at least ) queries, dunno if this changed in 8.1
BTW, did someone go further with that idea? If not I'd like rewrite
that stuff in C ( I do prefer C++ ).
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 2
and the service relocation
worked as expected.
Consider also that applications shall have a good behaviour like try to
close the current connection and retry to open a new one for a while
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 5: don't forget
Gaetano Mendola wrote:
Alvaro Herrera wrote:
On Mon, Sep 26, 2005 at 05:41:24PM +0200, Gaetano Mendola wrote:
Joshua D. Drake wrote:
Autovacuum is integrated into the backend for 8.1
Can I set the autovacuum parameter per table instead of per
engine ?
Yes.
Reading the 8.1 release note I
of an average engine usage and other
tables are so huge to not be analyzed for months.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command
Gaetano Mendola
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
Alvaro Herrera wrote:
On Mon, Sep 26, 2005 at 05:41:24PM +0200, Gaetano Mendola wrote:
Joshua D. Drake wrote:
Autovacuum is integrated into the backend for 8.1
Can I set the autovacuum parameter per table instead of per
engine ?
Yes.
Finally :-)
good work.
Regards
Gaetano Mendola
the SRPMS I can create the rpms and give them
to you
Regards
Gaetano Mendola
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCkx4W7UpzwH2SGd4RAp4uAKCdobiXlhZkc6TzersTA295ne0GggCgreVU
ftk/gM7gvdMSoRkKhSb2Il4=
=63o7
Dave Cramer wrote:
Check the archives, this has already been discussed.
Devrim is posting a compat rpm shortly.
Thx.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I understood that noone will add that option to pglib,
is it correct ?
Regards
Gaetano Mendola
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
.
Regards
Gaetano Mendola
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCi04C7UpzwH2SGd4RArvMAKDUJEefpsH2CX9E6wjg2j5DcV3JSwCgr/XB
BlTc3y4vE9GjyUl6eypcN00=
=h/Gg
-END PGP SIGNATURE
Oliver Jowett wrote:
If you're unlucky, the server could go down while you're blocked waiting
for a query response..
That is exactly what happens to us, and you have to be not so unlucky for
that happen if the engine have ~100 query at time.
Regards
Gaetano Mendola
option ?
Regards
Gaetano Mendola
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCiJNF7UpzwH2SGd4RAh8aAJ0WOBEzzjYf1gj1OaFGsFBE9mr4hgCfUhna
D1F420Pa94lvrA04xA73tiE=
=muzn
-END PGP SIGNATURE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hannu Krosing wrote:
Ühel kenal päeval (teisipäev, 8. märts 2005, 00:52+0100), kirjutas
Gaetano Mendola:
Hi all,
running a 7.4.5 it happen to me with another table
where a single vacuum full was not freeing enough pages,
here the verbose vacuum
.
Sorry, I was convinced to have sent this email to performances ( as I do
usually ).
Regards
Gaetano Mendola
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCLXih7UpzwH2SGd4RApCYAKCS/1qPYFs7GABfpwAO0c51kg
rather than
1-in-2^32. I was dubious about this at the time, but didn't have any
evidence showing that we shouldn't go for 64. I suppose we ought to try
the same example with a 32-bit CRC and see how much it helps.
Continuing this why not a 16-bit then ?
Regards
Gaetano Mendola
.
Regards
Gaetano Mendola
# vacuum full verbose url;
INFO: vacuuming public.url
INFO: url: found 268392 removable, 21286 nonremovable row versions in 8563
pages
DETAIL: 22 dead row versions cannot be removed yet.
Nonremovable row versions range from 104 to 860 bytes long.
There were 13924 unused
Gaetano Mendola
---(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
will not offer only marginal performance improvements. I see some
time my 4-CPU server with 3 CPU in holiday and other CPU working on a long
sequential scan. I hope that this patch, if it works correctly will be used
in future Postgresql version
Regards
Gaetano Mendola
Greg Stark wrote:
Gaetano Mendola [EMAIL PROTECTED] writes:
We do ~4000 txn/minute so in 6 month you are screewd up...
Sure, but if you ran without vacuuming for 6 months, wouldn't you notice the
huge slowdowns from all those dead tuples before that?
In my applications yes, for sure
a couple years to get there.
We do ~4000 txn/minute so in 6 month you are screewd up...
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
an automatic vacuum instead of shutdown ? At least the
DB do not stop working untill someone study what the problem is and
how solve it.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom Lane wrote:
| Gaetano Mendola [EMAIL PROTECTED] writes:
|
|my warning was due the fact that in the docs is written nowhere this
|drawback.
|
|
| The SELECT reference page already says that the output rows are computed
| before applying ORDER
one? Shall be not documented ?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Greg Stark wrote:
Gaetano Mendola [EMAIL PROTECTED] writes:
now what do I see is that for each different x value
the foo is executed more than once, I guess this is because
the distinct filter out the rows after executing the query.
Is this behaviour the normal one? Shall be not documented
set on this, but it feels cleaner.
you're right. Let's go for timestamptz and let the users decide ...
Well, the unix guys have the abit to have the uptime as an interval, I'm
inclined to have boths: pg_uptime ( interval ) and pg_starttime (
timestamptz )
Regards
Gaetano Mendola
=# select sp_test('test1');
NOTICE: ID -1
NOTICE: ID -1
sp_test
-
0
(1 row)
test=# select sp_test('test2');
NOTICE: ID -1
NOTICE: ID -1
sp_test
-
0
(1 row)
Regards
Gaetano Mendola
---(end of broadcast
...
Did you updated the CVS ?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
Tom Lane wrote:
Gaetano Mendola [EMAIL PROTECTED] writes:
I'm having a bounce of errors because IMMUTABLE and STABLE
attributes for some of my functions. Let me explain with an example,
Hmm. This particular example is a bug in exec_eval_simple_expr() ...
if we're going to bypass SPI then we'd
is a good idea write in the release notes, with a bigger font,
this
optimization about stable and immutable functions.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 8: explain analyze is your friend
queries
Yes, this will shift postgresql in Sybase direction.
Did you solved also all your concerns on my two bash scripts ?
Are that scripts eligibles to be putted in contrib ?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 3: if posting/reading
Marc G. Fournier wrote:
If there were a comp.databases.postgresql.hackers newsgroup created and
carried by all the news servers ... would you move to using it vs using
the mailing lists?
No.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 2
Thomas Hallgren wrote:
Gaetano Mendola wrote:
...so the very first client is the real server
that must be run 24/24.
I don't think this is correct. You need a tracker for downloaders to be
able to find each other but no client is more important than the others.
I'm sorry to say that you're wrong
that is launched
pointing to the complete file; so the very first client is the real server
that must be run 24/24.
What do you have against the python implementation ?
Regards
Gaetano Mendola
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http
not.
At my knowledge Postgres can read that file even if it's writable by
anyone ( I can not test right now or look at the code), if this is the
case then this is a sort of serious bug :-(
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 9
where it is broken there is nothing
we can do about it.
Like what? If the OS can not handle UDP reassembly then we have some other
problems
around
I think the OS breakage is a non issue here.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 1
during the make check.
BTW: is there some free tool that do the Rational Coverage work ?
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Hi all,
it seems that the tracker is down or at least not reachable.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Fetter wrote:
| On Sun, Nov 07, 2004 at 10:53:22PM +0100, Gaetano Mendola wrote:
|
|Hi all,
|it seems that the tracker is down or at least not reachable.
|
|
| Started again. Thanks for the notice. :)
Indeed now it's working.
| BTW, do you have
1 - 100 of 411 matches
Mail list logo
