On Thu, Sep 22, 2005 at 03:52:21PM +1000, Gavin Sherry wrote:
> On Wed, 31 Aug 2005, Tom Lane wrote:
>
> > BTW ... the original Berkeley papers on Postgres make frequent reference
> > to a "vacuum daemon", which seems to be essentially what we're trying to
> > build with autovacuum. Does anyone k
On Wed, 31 Aug 2005, Tom Lane wrote:
> BTW ... the original Berkeley papers on Postgres make frequent reference
> to a "vacuum daemon", which seems to be essentially what we're trying to
> build with autovacuum. Does anyone know if the Berkeley implementation
> ever actually had auto vacuuming, o
On K, 2005-09-21 at 20:34 -0400, Rod Taylor wrote:
> Sure. But if you are using STDOUT then why does this need to be a server
> side item at all?
>
> You either have code issuing the commands and collecting the results
> making a standard select just as fast or you are using psql which
> already h
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Confusion fixed (thanks, Tom). psql (via libpq) tries twice, if not
> given a password to begin with (via .pgpass or psql's -W).
> Ugly but at least not incomprehensible.
This seems reasonable behavior when prompting for a password from the
user, since
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> I am puzzled about this. The strace output below is from CVS tip and
> shows the postmaster and children during a single (local) connection
> when the auth method is md5.
libpq is designed to abandon the connection and retry in certain
circumstances .
Andrew Dunstan wrote:
>
>
> Bruce Momjian wrote:
>
> >Andrew Dunstan wrote:
> >
> >
> Example (log_line_prefix = '%t [EMAIL PROTECTED] %r %p %c:%l'):
>
> 2005-09-19 19:16:39 EDT [EMAIL PROTECTED] 6541 432f46d7.198d:1 LOG:
> connection received: host=[local] port=
>
Andrew Dunstan wrote:
I am puzzled about this. The strace output below is from CVS tip and
shows the postmaster and children during a single (local) connection
when the auth method is md5. What we see is 2 calls to clone() (that's
Linux for fork(), more or less). When the auth method is se
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Rod Taylor wrote:
>> Writing a file on the server requires significant privilege, including
>> access to the server itself so you can retrieve the results.
> But we also do COPY to STDOUT which requires no special privileges on
> the server.
Currently
I am puzzled about this. The strace output below is from CVS tip and
shows the postmaster and children during a single (local) connection
when the auth method is md5. What we see is 2 calls to clone() (that's
Linux for fork(), more or less). When the auth method is set to trust or
ident, ther
Rod Taylor wrote:
You either have code issuing the commands and collecting the results
making a standard select just as fast or you are using psql which
already has multiple display types for SELECT data, including XML
output, but another could easily be added for CSV style output.
We ha
On Wed, 2005-09-21 at 19:55 -0400, Andrew Dunstan wrote:
>
> Rod Taylor wrote:
>
> >On Wed, 2005-09-21 at 15:25 -0700, Trent Shipley wrote:
> >
> >
> >>
> >>Wouldn't you also need a CREATE TEMP TABLE privilege but the
> >>COPY TO file USING select_statement
> >>would only need select. (In oth
Rod Taylor wrote:
On Wed, 2005-09-21 at 15:25 -0700, Trent Shipley wrote:
Wouldn't you also need a CREATE TEMP TABLE privilege but the
COPY TO file USING select_statement
would only need select. (In other words using a temp table would not seem to
be as secure nor as general as the req
On Wed, 2005-09-21 at 15:25 -0700, Trent Shipley wrote:
> On Wednesday 2005-09-21 07:01, Hans-Jürgen Schönig wrote:
> > Rod Taylor wrote:
> > >>the problem is: COPY can write data returned by a SELECT statement to a
> > >>file. our idea is to implement precisely that.
> > >>
> > >>example:
> > >>
>
On Wednesday 2005-09-21 07:01, Hans-Jürgen Schönig wrote:
> Rod Taylor wrote:
> >>the problem is: COPY can write data returned by a SELECT statement to a
> >>file. our idea is to implement precisely that.
> >>
> >>example:
> >>
> >>COPY TO file_name USING some_select_statement;
> >
> > I have run i
Hi,
I tried to compile PL/Java against PostgreSQL 8.1beta2. I use pgxs and
until now that has been just fine. Now pgxs suggests that the include
files reside under /usr/local/pgsql. They don't of course. Not on my
windows box anyway :-)
I think it stems from the src/Makefile.global. On line 5
On K, 2005-09-21 at 15:39 -0400, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > Is it possible that the Release Notes do not fully explain the
> > Constraint Exclusion feature? Or is it the consensus that it works but
> > not quite well enough to make a song and dance about yet?
>
>
On K, 2005-09-21 at 18:10 +0100, Simon Riggs wrote:
> Table Partitioning is in 8.1
>
> I've just read Peter Eisentraut's presentation to the Dutch gov (very
> good BTW). On the last page I read that Table Partitioning is a future
> for PostgreSQLwhich is strange because Constraint Exclusion is
"William ZHANG" <[EMAIL PROTECTED]> writes:
> # These settings are initialized by initdb -- they might be changed
> lc_messages = 'Chinese_People''s Republic of China.936' # locale for
> system error message
Bruce seems to have gotten a bit ahead of himself on the
SQL-standard-strings proj
Michael Fuhr <[EMAIL PROTECTED]> writes:
> pg_dump emits COMMENT ON DATABASE (if the database has a comment)
> even when dumping only an individual schema or table. That seems
> inappropriate,
Agreed, this seems like a bug. Fix applied.
regards, tom lane
---
Bruce Momjian wrote:
Andrew Dunstan wrote:
Example (log_line_prefix = '%t [EMAIL PROTECTED] %r %p %c:%l'):
2005-09-19 19:16:39 EDT [EMAIL PROTECTED] 6541 432f46d7.198d:1 LOG:
connection received: host=[local] port=
In the case above, I rather expected %q to kick in.
Simon Riggs <[EMAIL PROTECTED]> writes:
> Is it possible that the Release Notes do not fully explain the
> Constraint Exclusion feature? Or is it the consensus that it works but
> not quite well enough to make a song and dance about yet?
I hardly think that the existing constraint-exclusion code i
Simon Riggs wrote:
> On Mon, 2005-09-19 at 13:21 -0400, Bruce Momjian wrote:
>
> > OK. I tested it and it actually works
>
> Gosh, that says a lot about my code quality. I will strive to improve
> from "actually works" to "works as expected" for future patches.
>
> > and I added documentation
>
On Wed, Sep 21, 2005 at 06:10:15PM +0100, Simon Riggs wrote:
> Table Partitioning is in 8.1
>
> I've just read Peter Eisentraut's presentation to the Dutch gov (very
> good BTW). On the last page I read that Table Partitioning is a future
> for PostgreSQLwhich is strange because Constraint Exc
In the past couple years I've worked on several personal/business
projects to cluster PostgreSQL and InnoDB (without MySQL). I've
tested shared-nothing, shared-memory, and shared-disk models.
IMHO, shared-disk is the only viable option for performance and/or
large production business environments
[EMAIL PROTECTED] ("Joshua D. Drake") writes:
> Hans-Jürgen Schönig wrote:
>> no because a new is not a heap ...
>
> Why not use a function with a temporary table?
>
> That way you can pass a table parameter that
> is the temporary table with a select statement
> that you can populate the temp tabl
No I do not have a case study, I just read so, but what I am suggesting to
start doing is that if there is no cluster implementation to give high
availability of the database, I will start doing this project through the
message passing technique and I already have in the university a cluster of
19
I think its a great idea to give it a shot, maybe you can present a
proposal to the list of how you wish to go about it. There could be some
experts on the list who may give you some input and direction.
Aly.
David Fetter wrote:
On Wed, Sep 21, 2005 at 08:01:08PM +0300, Rafik Salama wrote:
On Wed, Sep 21, 2005 at 08:01:08PM +0300, Rafik Salama wrote:
> Dear Sirs
>
> I know that that postgresql can be configured for high availability
> over a clustered environment using pgcluster,
Do you have a case study showing this?
> I am currently studying in my masters the clustering using MP
Table Partitioning is in 8.1
I've just read Peter Eisentraut's presentation to the Dutch gov (very
good BTW). On the last page I read that Table Partitioning is a future
for PostgreSQLwhich is strange because Constraint Exclusion is an
8.1 feature.
I've had five other people ask about it too
Dear Sirs
I know that that postgresql can be configured for high
availability over a clustered environment using pgcluster, I am currently
studying in my masters the clustering using MPI and OpenMP, PVM and others
packages and I have to do a project, so I was thinking to use this opport
On Wednesday 21 September 2005 01:10, Michael Fuhr wrote:
> pg_dump emits COMMENT ON DATABASE (if the database has a comment)
> even when dumping only an individual schema or table. That seems
> inappropriate, especially when copying data to a different cluster
> where the named database might not
So, that means copy doesn't support views? If it is like that, then why not
work in the View support for the Copy statement?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Hans-Jürgen Schönig
Sent: Miércoles, 21 de Septiembre de 2005 08:04 a.m.
To: Paolo
> > Hi,
> > I just installed the PostgreSQL 8.1-beta2 on my Windows box
> using the
> > windows installer. I then try to compile PL/Java. It fails to find
> > pgxs.
> > Is it moved to somewhere else? Or is it not included?
>
> It's not installed by default, but when it is selected it
> lives u
On Mon, 2005-09-19 at 13:21 -0400, Bruce Momjian wrote:
> OK. I tested it and it actually works
Gosh, that says a lot about my code quality. I will strive to improve
from "actually works" to "works as expected" for future patches.
> and I added documentation
> suggesting its usage.
> !
Hans-Jürgen Schönig wrote:
no because a new is not a heap ...
Why not use a function with a temporary table?
That way you can pass a table parameter that
is the temporary table with a select statement
that you can populate the temp table with.
Sincerely,
Joshua D. Drake
em=# create vie
Joshua D. Drake wrote:
Hans-Jürgen Schönig wrote:
no because a new is not a heap ...
Why not use a function with a temporary table?
That way you can pass a table parameter that
is the temporary table with a select statement
that you can populate the temp table with.
Sincerely,
Joshua D. D
Andrew Dunstan wrote:
>
>
> Bruce Momjian wrote:
>
> >Andrew Dunstan wrote:
> >
> >
> >>While preparing for a presentation, I noticed some mildly ugly effects
> >>with log_line_prefix during session startup if log_connections is turned on.
> >>
> >>Example (log_line_prefix = '%t [EMAIL PROTEC
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Thomas Hallgren
> Sent: 21 September 2005 15:54
> To: PostgreSQL-development
> Cc: [EMAIL PROTECTED]
> Subject: [HACKERS] Where is pgxs?
>
> Hi,
> I just installed the PostgreSQL 8.1-beta2 on my
=?ISO-8859-1?Q?Hans-J=FCrgen_Sch=F6nig?= <[EMAIL PROTECTED]> writes:
> COPY TO file_name USING some_select_statement;
I think this has been discussed before, check the archives.
> to implement the desired feature we just had to add some SPI code to the
> scenery (SPI will also return HeapTuples
Hi,
I just installed the PostgreSQL 8.1-beta2 on my Windows box using the
windows installer. I then try to compile PL/Java. It fails to find pgxs.
Is it moved to somewhere else? Or is it not included?
Regards,
Thomas Hallgren
---(end of broadcast)
=?ISO-8859-1?Q?Hans-J=FCrgen_Sch=F6nig?= <[EMAIL PROTECTED]> writes:
> Paolo Magnoli wrote:
>> Can't you just use a view?
> no because a new is not a heap ...
I think Paolo's idea is much better than munging the syntax of COPY,
though. Fixing COPY so that you *could* copy from a view would provi
no because a new is not a heap ...
em=# create view x as select * from pg_class;
CREATE VIEW
em=# copy x to '/tmp/x';
ERROR: cannot copy from view "x"
best regards,
hans
Paolo Magnoli wrote:
Can't you just use a view?
-Messaggio originale-
Da: [EMAIL PROTE
Can't you just use a view?
-Messaggio originale-
Da: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] conto di Hans-Jürgen
Schönig
Inviato: mercoledì 21 settembre 2005 15.30
A: pgsql-hackers@postgresql.org; [EMAIL PROTECTED]
Oggetto: [HACKERS] feature proposal ...
hackers,
currently we have
Rod Taylor wrote:
the problem is: COPY can write data returned by a SELECT statement to a
file. our idea is to implement precisely that.
example:
COPY TO file_name USING some_select_statement;
I have run into plenty of cases where I wanted to dump part of a
structure and this could be used
> the problem is: COPY can write data returned by a SELECT statement to a
> file. our idea is to implement precisely that.
>
> example:
>
> COPY TO file_name USING some_select_statement;
I have run into plenty of cases where I wanted to dump part of a
structure and this could be used for that,
hackers,
currently we have to hack tons of export scripts for various customers.
the problem is: if tables can be exported straight forward COPY will
give you all you need but when data has to be transformed while
exporting things start becoming a bit more complex. usually people want
to have
On Wed, Sep 21, 2005 at 08:47:04AM +0300, Hannu Krosing wrote:
> On K, 2005-09-21 at 09:01 +0400, Oleg Bartunov wrote:
> > it'd be nice if parameters could be passed at the creation time only and
> > somehow stored, so other functions could retrieve them. It's not
> > convenient but also safe.
>
What you find is in initdb.c. Maybe the author want to make single quotes
escaped just the same as in SQL. But guc-file.l is unaware of it.
"Qingqing Zhou" <[EMAIL PROTECTED]> wrote
>
> Diff current version vs. some earlier version, you see this:
>
> /*
> * signal handler in case we are interr
Hi Peter!
I would like to join the translation project. I am already translator in
the press releases project. My pgfoundry user id is 'k0cka'
Thanks,
Laszlo
Peter Eisentraut wrote:
I think beta 2 is a good time to start fixing up the translations again.
As I had previously announced, long
49 matches
Mail list logo
