I have tried to compile 8.1.3 with mingw but I am receiving
come errors, I do not know with versions are the correct one.
Could some body tell me the right versions ? and url's to
download from ? please. I searched the mainling lists but it
is not clear.
Magnus Hagander has pointed me
I'm looking for some comphrensive article explaining the Optimizer, i.e
detailed explanation on Hash joins, Nested Joins etc., and why would the Optimizer choose that.
can anybody point me to some good tutorials and resources?
regards,
Luckys
I have written some experimental code of doing master-slave seqscan in
PostgreSQL. During the work, I feel we had enough infrastructure to support
parallel query execution.
What I did is adding a new node PARA and plug it above the node that we want
to execute in parallel. In this stage, a PARA
On Thu, Apr 06, 2006 at 06:28:33PM +0800, Qingqing Zhou wrote:
I have written some experimental code of doing master-slave seqscan in
PostgreSQL. During the work, I feel we had enough infrastructure to support
parallel query execution.
Good work. One question though, temporary tables.
On Wed, Apr 05, 2006 at 11:55:15PM -0300, Marc G. Fournier wrote:
On Wed, 5 Apr 2006, Jim Nasby wrote:
One idea that comes to mind is to come up with a list of popular OSS
projects that we'd like to see add PostgreSQL support and have students
work on those...
As nice an idea as this
2006/4/6, Luckys [EMAIL PROTECTED]:
I'm looking for some comphrensive article explaining the Optimizer, i.e
detailed explanation on Hash joins, Nested Joins etc., and why would the
Optimizer choose that.
can anybody point me to some good tutorials and resources?
A Tour of PostgreSQL
On 4/6/06, Qingqing Zhou [EMAIL PROTECTED] wrote:
I have written some experimental code of doing master-slave seqscan in
PostgreSQL. During the work, I feel we had enough infrastructure to support
parallel query execution.
Great work! I had looked into this a little bit and came to the same
mydb=# select to_timestamp(' 0300','mmdd hh24mi');
to_timestamp
---
0001-01-01 03:00:00+01 BC
(1 row)
Questionable, but probably valid.
mydb=# select to_timestamp(' 0300','mmdd hh24mi');
to_timestamp
Am Donnerstag, 6. April 2006 14:57 schrieb Mario Weilguni:
mydb=# select to_timestamp(' 0300','mmdd hh24mi');
to_timestamp
---
0001-01-01 03:00:00+01 BC
(1 row)
Questionable, but probably valid.
mydb=# select to_timestamp('
On Thursday 06 April 2006 07:43, Nicolas Barbier wrote:
2006/4/6, Luckys [EMAIL PROTECTED]:
I'm looking for some comphrensive article explaining the Optimizer, i.e
detailed explanation on Hash joins, Nested Joins etc., and why would the
Optimizer choose that.
can anybody point me to some
Hello Folks,
This may be a dumb question but please bear a moment with me.
About the TODO item %Allow pg_hba.conf settings to be controlled via
SQL: If in the future we could configure the settings by SQL commands,
assuming the settings are saved in an internal table, what would be the
need for
-bugs is getting inundated with windows installer bugs, and people on
the list don't seem to be replying to them. Can someone with the
installer project add more prominent information about where users
should be reporting installer bugs to? (I'm guessing that the
installer has a bug
Tom Lane wrote:
Hi,
It would be just a small change to make the code cache the EState across
calls, saving a link to it in the FmgrInfo, but I am worried about that.
If the EState's query context is made to be a child of the memory
context containing the caller's FmgrInfo, then there is no
It does, and it's listed on the page. It clearly states use the
mailinglists for general stuff, and the trackers for installer specific
issues.
However, this is the official installer for pg on win32. And I'd expect
a lot of new users not to know (or understand) the distinction that the
installer
Alvaro Herrera [EMAIL PROTECTED] writes:
This is a shot in the dark, but I remember you commenting awhile back
that there was a way to register a callback to be called on memory
context reset or delete.
AFAIR there's no such thing associated with memory contexts per se.
There is one for
Magnus Hagander wrote:
Now, it would certainly help if more people could actually help in
*answering* the bugs/questions that are posted :), but that's a
different question...
//Magnus
I have created a very nice installer using Inno setup and it is about 50
times easier to code for than the
Gevik Babakhani wrote:
This may be a dumb question but please bear a moment with me.
About the TODO item “%Allow pg_hba.conf settings to be controlled via
SQL“: If in the future we could configure the settings by SQL commands,
assuming the settings are saved in an internal table, what would be
Gevik Babakhani schrieb:
Hello Folks,
This may be a dumb question but please bear a moment with me.
About the TODO item “%Allow pg_hba.conf settings to be controlled via
SQL“: If in the future we could configure the settings by SQL commands,
assuming the settings are saved in an internal table,
Jonah H. Harris wrote:
On 4/6/06, Qingqing Zhou [EMAIL PROTECTED] wrote:
I have written some experimental code of doing master-slave seqscan in
PostgreSQL. During the work, I feel we had enough infrastructure to support
parallel query execution.
Great work! I had looked into this a
On Thursday 06 April 2006 09:45, Gevik Babakhani wrote:
Hello Folks,
This may be a dumb question but please bear a moment with me.
About the TODO item %Allow pg_hba.conf settings to be controlled via
SQL: If in the future we could configure the settings by SQL commands,
assuming the
I agree. Security is a good reason to have the pg_bha.conf around. I guess
it would make the TODO item a bit harder to develop hence one has to read
and write the file to support the future SQL commands too. I also looked
at the code for a moment; perhaps using a yacc/lex mechanism would make
[EMAIL PROTECTED] (Gevik Babakhani) writes:
This may be a dumb question but please bear a moment with me. About
the TODO item %Allow pg_hba.conf settings to be controlled via
SQL: If in the future we could configure the settings by SQL
commands, assuming the settings are saved in an internal
i have continued the pgadmin III's Chinese simplified
translations,hope this translate will release with the next version
of pgadmin III.thanks. how can i submit this translate-- 我渴望平静，风却给了我涟漪
Jonah H. Harris [EMAIL PROTECTED] wrote
Great work! I had looked into this a little bit and came to the same
ideas/problems you did, but none of them seemed insurmountable at all.
I'd be interested in working with you on this if you'd like.
Yes, I am happy to work with anyone on the
=?ISO-8859-2?Q?Horv=E1th_S=E1ndor?= [EMAIL PROTECTED] writes:
In the documentation:
CREATE CONSTRAINT TRIGGER is used within CREATE TABLE/ALTER TABLE and
by pg_dump to create the special triggers for referential integrity. It
is not intended for general use.
What means it is not intended
Mario Weilguni [EMAIL PROTECTED] writes:
I think all except the first one should raise a warning, isn't it?
to_timestamp (and friends) all seem to me to act pretty bizarre when
faced with input that doesn't match the given format string. However,
in the end that is an Oracle-compatibility
On Thu, Apr 06, 2006 at 03:55:20PM +0200, Magnus Hagander wrote:
Now, it would certainly help if more people could actually help in
*answering* the bugs/questions that are posted :), but that's a
different question...
Well, that's my primary concern. It seems that people aren't replying to
27 matches
Mail list logo
