On Thu, May 27, 2004 at 23:02:42 +,
Peter Galbavy <[EMAIL PROTECTED]> wrote:
> Bruno Wolff III wrote:
> >For long running transactions where you want to recover as much as
> >possible,
> >one might also want to recover up until just before a specific transaction
> >committed (as opposed to s
Is it worth us marking any system catalog indexes as clusterable by
default for performance?
Chris
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
No check is performed for being a superuser, the table owner or that it
is a system table when marking an index for clustering:
usa=> alter table pg_class cluster on "pg_class_oid_index";
ALTER TABLE
usa=> select oid from pg_class where relname='pg_class_oid_index';
oid
---
16613
(1 row)
u
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Here are features that are being worked on, hopefully for 7.5:
> o tablespaces (Gavin)
> o nested transactions (Alvaro)
> o two-phase commit (Heikki Linnakangas)
> o integrated pg_autovacuum (O'Connor)
> o PITR (Riggs)
>
Alexey Borzov wrote:
Hi!
Tim Conrad wrote:
My favourite part of it is:
MySQL uses traditional row-level locking. PostgreSQL uses something
called Multi Version Concurrency Control (MVCC) by default. MVCC is
a little different from row-level locking in that transactions on
the database a
Tom Lane wrote:
> Neil Conway <[EMAIL PROTECTED]> writes:
> > Most of your suggestions are agreeable; a few minor quibbles follow.
>
> >> lfirstcell new function to get first cell, or NULL if none
> > [...]
> >> llastnode llastcell
>
> > What do you think of list_head() and list_tail() instead?
Manfred Koizar <[EMAIL PROTECTED]> writes:
> Is there a special reason for scanning the leaf pages in *logical*
> order, i.e. by following the opaque->btpo_next links?
Yes. Read the README file concerning interlocking between indexscans
and deletions.
regards, tom lane
-
Simon Riggs wrote:
> On Tue, 2004-04-27 at 21:56, Rod Taylor wrote:
> > > Overall, I'd refer back to the points Bruce raised - you certainly do
> > > need a way of finding out the time to recover to, and as others have
> > > said also, time isn't the only desirable "recovery point".
> >
> > Wouldn
Hi
thank you for such a useful information...
but actually in my case if i keep table in disk it significantly
degrades performance and even for a table of 10 rows it takes 1-2
minutes I think u r not beliving it ! am i right
for example
I create a table in which i use my customized data
Andrew Payne wrote:
> Also, Apache never had "MyApache", a more popular version that many believe
> to be "free" and "open source".
>
> My point: Apache was successful in a situation that may not apply here.
>
> Does anyone know of an open source project that *has* successfully displaced
> a mar
Joshua D. Drake wrote:
I know both. :-).
Seriously - I'd like to raise my voice in favor of installing plpgsql
in template1 by default. I haven't heard any good reason not to (nor
even a bad reason).
If we install plPGSQL by default, we should install any other pl
language that was configured a
On the other topics...
I think the biggest service PGSQL could provide to the open source
community is a resource that teaches people with no database experience
the fundamentals of databases. If people had an understanding of what a
RDBMS should be capable of and how it should be used, they wouldn
Neil Conway <[EMAIL PROTECTED]> writes:
> Most of your suggestions are agreeable; a few minor quibbles follow.
>> lfirstcell new function to get first cell, or NULL if none
> [...]
>> llastnodellastcell
> What do you think of list_head() and list_tail() instead?
No strong objection, though
Seriously - I'd like to raise my voice in favor of installing
plpgsql in
template1 by default. I haven't heard any good reason not to
(nor even a
bad reason).
It has to work with older dumps that will try to recreate pl/pgsql
themselves explicitly.
I offered the same opinion a while back, and
If anything, I'd rather see the JDBC and ODBC drivers reinstated in the
release. More than 56% of the PostgreSQL users (according to the poll) uses
JDBC today. ODBC is merely 18% but that might change significantly when the
native Win32 port is released. I might have missed something altogether
her
Joshua D. Drake wrote:
If we install plPGSQL by default, we should install any other pl
language that was configured at runtime by default as well. This
includes plPerl, plTCL, and plPython.
Of course only if they were compiled in, but sense they are a part of
the core distribution we shouldn'
Another idea would be to provide some means to roll a database forwards
and backwards. If you're doing a recovery because you did something like
an accidental UPDATE SET field = blah without a where clause, what you
really care about is going up to the point right before that update. If
there's a l
On Tue, Apr 27, 2004 at 01:14:08PM -0700, Joshua D. Drake wrote:
> If we install plPGSQL by default, we should install any other pl
> language that was configured at runtime by default as well. This
> includes plPerl, plTCL, and plPython.
That certainly makes sense.
> Of course only if they were
On Tue, 2004-04-27 at 23:47, Jonathan Gardner wrote:
> I've just discovered OLAP and it looks like a competing technology with
> materialized views.
Yes. Read up some more, but don't get sucked in by the marketing.
> In a nutshell, OLAP seems to be "pre-storing" the results of potential
> queri
On Tue, Apr 27, 2004 at 01:32:44PM -0700, Dann Corbit wrote:
> > From: Andrew Dunstan [mailto:[EMAIL PROTECTED]
> > Seriously - I'd like to raise my voice in favor of installing
> > plpgsql in template1 by default. I haven't heard any good reason not
> > to (nor even a bad reason).
>
> I offere
I've just discovered OLAP and it looks like a competing technology with
materialized views.
In a nutshell, OLAP seems to be "pre-storing" the results of potential
queries. When queries are made with those conditions, then the pre-stored
results are used. It seems most common for join conditions
On Tue, 2004-04-27 at 23:11, Rod Taylor wrote:
> On Tue, 2004-04-27 at 17:36, Simon Riggs wrote:
> > On Tue, 2004-04-27 at 21:56, Rod Taylor wrote:
> > > > Overall, I'd refer back to the points Bruce raised - you certainly do
> > > > need a way of finding out the time to recover to, and as others h
On Fri, 2004-05-28 at 00:02, Peter Galbavy wrote:
> Bruno Wolff III wrote:
> > For long running transactions where you want to recover as much as possible,
> > one might also want to recover up until just before a specific transaction
> > committed (as opposed to started).
>
> If your DB has died
On Tue, 2004-04-27 at 21:56, scott.marlowe wrote:
> On Mon, 26 Apr 2004, Andrew Payne wrote:
>
> >
> > Bruce asked an excellent question:
> >
> > > My question is, "What can we learn from MySQL?" I don't know there is
> > > anything, but I think it makes sense to ask the question.
> >
Ignore
On Tue, 2004-04-27 at 17:36, Simon Riggs wrote:
> On Tue, 2004-04-27 at 21:56, Rod Taylor wrote:
> > > Overall, I'd refer back to the points Bruce raised - you certainly do
> > > need a way of finding out the time to recover to, and as others have
> > > said also, time isn't the only desirable "rec
Bruno Wolff III wrote:
For long running transactions where you want to recover as much as possible,
one might also want to recover up until just before a specific transaction
committed (as opposed to started).
If your DB has died and you are recovering it, how do you reestablish a
session so that
On Tue, 2004-04-27 at 21:56, Rod Taylor wrote:
> > Overall, I'd refer back to the points Bruce raised - you certainly do
> > need a way of finding out the time to recover to, and as others have
> > said also, time isn't the only desirable "recovery point".
>
> Wouldn't it be sufficient to simply u
On Mon, 26 Apr 2004, Andrew Payne wrote:
> For those that look to Apache: Apache never had a well-established
> incumbent (Oracle), an a well-funded upstart competitor (MySQL). Rob
> McCool's NCSA httpd (and later, Apache) were good enough and developed
> rapidly enough that they prevented any o
Jim C. Nasby wrote:
Maybe also a more generic section about how PGSQL is different from
other databases. Maybe I'm just dense, but it took me a long time to
figure out the whole lack of stored procedures thing (yes, PGSQL
obviously has the functionality, but many experienced DBAs won't
associate fu
On Wed, 21 Apr 2004, Shalu Gupta wrote:
> Hello,
>
> We are trying to import the TPC-H data into postgresql using the COPY
> command and for the larger files we get an error due to insufficient
> memory space.
>
> We are using a linux system with Postgresql-7.3.4
>
> Is it that Postgresql canno
On Wed, 21 Apr 2004 [EMAIL PROTECTED] wrote:
> Hi
> I am working on a project in postgres..in which i designed customized data type
> and operations on it.it requires a look up table..
> I have three options regarding this table...
> 1. Every time a query is executed it creates table assigns value
On Mon, 26 Apr 2004, Andrew Payne wrote:
>
> Bruce asked an excellent question:
>
> > My question is, "What can we learn from MySQL?" I don't know there is
> > anything, but I think it makes sense to ask the question.
>
> After watching the traffic on this, the biggest MySQL lesson has gone
>
> Overall, I'd refer back to the points Bruce raised - you certainly do
> need a way of finding out the time to recover to, and as others have
> said also, time isn't the only desirable "recovery point".
Wouldn't it be sufficient to simply use the transaction ID and ensure
that all the parameters
On Mon, 2004-04-26 at 17:24, Manfred Koizar wrote:
> On Mon, 26 Apr 2004 14:29:58 +0100, Simon Riggs <[EMAIL PROTECTED]>
> wrote:
> >> Now that FSM
> >> covers free btree index pages this access pattern might be highly
> >> nonsequential.
> >
> >I had considered implementing a mode where the inde
On Tue, 2004-04-27 at 18:10, Peter Eisentraut wrote:
> Simon Riggs wrote:
> > New utility aimed at being located in src/bin/pg_arch
>
> Why isn't the archiver process integrated into the server?
>
Number of reasons
Overall, I initially favoured the archiver as another special backend,
like
> -Original Message-
> From: Andrew Dunstan [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 27, 2004 12:55 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [HACKERS] Usability, MySQL, Postgresql.org,
> gborg, contrib,
>
>
> Jim C. Nasby wrote:
>
> >
> >I would still argue that if any langua
I know both. :-).
Seriously - I'd like to raise my voice in favor of installing plpgsql in
template1 by default. I haven't heard any good reason not to (nor even a
bad reason).
If we install plPGSQL by default, we should install any other pl
language that was configured at runtime by defaul
On Tue, 2004-04-27 at 18:43, Bruno Wolff III wrote:
> On Tue, Apr 27, 2004 at 10:38:45 +0100,
> Richard Huxton <[EMAIL PROTECTED]> wrote:
> >
> > Speaking as a DBA, what I usually want to do is restore to "immediately before
> > I started the payroll calculation". An actual wall-clock time is m
On Tue, 2004-04-27 at 08:56, Hans-Jürgen Schönig wrote:
> Simon Riggs wrote:
> > Since Phase1 is functioning and should hopefully soon complete, we can
> > now start thinking about Phase 2: full recovery to a point-in-time.
> >
> > Previous thinking was that a command line switch would be used t
On Tue, 2004-04-27 at 10:38, Richard Huxton wrote:
> On Tuesday 27 April 2004 00:32, Bruce Momjian wrote:
> > Simon Riggs wrote:
> > > On Mon, 2004-04-26 at 23:01, Alvaro Herrera wrote:
> > > > On Mon, Apr 26, 2004 at 05:05:41PM -0400, Bruce Momjian wrote:
> > > > > I was thinking --- how would so
Jim C. Nasby wrote:
I would still argue that if any language should be installed by default
it should be plpgsql and not java. As I mentioned, everyone using a
database already knows SQL; not nearly as many know java.
I know both. :-).
Seriously - I'd like to raise my voice in favor of installin
On Mon, Apr 26, 2004 at 02:31:27PM -0400, [EMAIL PROTECTED] wrote:
> > On Sun, Apr 25, 2004 at 05:15:19PM -0400, [EMAIL PROTECTED] wrote:
> >> (5) Programming languages. We need to make a programming language
> >> standard
> >> in PostgreSQL. plpgsql is good, but isn't someone working on a Java
> >
Ahh, perfect, thank you..
On Tue, 2004-04-27 at 16:18, Alvaro Herrera wrote:
> On Tue, Apr 27, 2004 at 09:26:38AM -0300, Chris Bowlby wrote:
>
> > I've been noticing that files in the pg_clog directory test to stay
> > around forever, I know they are used to determine the state of
> > transactio
On Tue, Apr 27, 2004 at 12:57:46PM -0400, Tim Conrad wrote:
> Seriously, though. I was looking through the list yesterday trying
> to figure out something, and it was kind of hard to do.But, more to
> my point, this stuff is in the MySQL manual, making it easy to find.
> (Yes. I know what MySQL in
I'm a great fan of Java. Still, I firmly believe that pgsql should be the
language of choice as the one included by default. I think many users
consider the ability to write functions and triggers using SQL intermixed
with the DDL statements (create function etc.) as the only natural way of
doing i
On Mon, Apr 26, 2004 at 21:31:33 -0400,
Andrew Payne <[EMAIL PROTECTED]> wrote:
>
> At some point (probably there now), I think the lack of a "Postgres, Inc."
> is going to hinder adoption. Companies want to 'buy' from vendors that look
> like real, viable companies, and provide them products w
scott.marlowe wrote:
I think the answer to all of this would require a lot of code being
touched to either make it case fold, costing performance, or the
replacement of the default lower cased catalog with upper cased catalog.
I'm not the one to decide, but it seems to me that this is not a go
Peter Eisentraut wrote:
> Simon Riggs wrote:
> > New utility aimed at being located in src/bin/pg_arch
>
> Why isn't the archiver process integrated into the server?
I think it is because the archiver process has to be started/stopped
independently of the server.
--
Bruce Momjian
On Tue, 27 Apr 2004, Jochem van Dieten wrote:
> [EMAIL PROTECTED] wrote:
> > (5) Programming languages. We need to make a programming language standard
> > in PostgreSQL. plpgsql is good, but isn't someone working on a Java
> > language. That would be pretty slick.
>
> IMHO SQL/PSM would be the o
On Mon, 26 Apr 2004, Josh Berkus wrote:
> > I think that a talented manager could make the case for certain features.
>
> So? So could any community member with a good grasp of database engineering
> and an ability to write persuasive e-mails.
I'd like to inject here that I was the one who st
Fabien COELHO wrote:
>
> Dear hackers,
>
> still in the spirit of "it may be useful to others, as it was to me, and
> it does cost very little", and before submitting a small patch and being
> exploded because it is obviously very stupid:
>
> Would it be appropriate to contribute BIT_AND and BIT
On Mon, 26 Apr 2004, Josh Berkus wrote:
> Shachar,
>
> > I think the concensus was that the runtime part was aprox. four lines
> > where the case folding currently takes place. Obviously, you would have
> > to get a var, and propogate that var to that place, but not actually
> > change program
On Tue, Apr 27, 2004 at 10:38:45 +0100,
Richard Huxton <[EMAIL PROTECTED]> wrote:
>
> Speaking as a DBA, what I usually want to do is restore to "immediately before
> I started the payroll calculation". An actual wall-clock time is mostly
> irrelevant to me.
For long running transactions wher
Simon Riggs wrote:
> New utility aimed at being located in src/bin/pg_arch
Why isn't the archiver process integrated into the server?
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.or
> > Not entirely true. I've read enough on the lists to see Bruce or
> > others saying 'x feature isn't expected until version y.z'. Heck, to
> > me, something that says 'we're hoping for feature x in version y.z',
> > but it's not an exact science. See the MySQL releases as an example
> > :)
>
>
On Tue, 27 Apr 2004, Tim Conrad wrote:
> On Tue, Apr 27, 2004 at 12:58:59PM -0300, Marc G. Fournier wrote:
> > On Tue, 27 Apr 2004, Tim Conrad wrote:
> >
> > > 2) There doesn't seem to be a clear roadmap on Postgres features.
> > >When certian things are expected. There's the TODO list that
>
Dear hackers,
still in the spirit of "it may be useful to others, as it was to me, and
it does cost very little", and before submitting a small patch and being
exploded because it is obviously very stupid:
Would it be appropriate to contribute BIT_AND and BIT_OR aggregates
for integer types, wit
Tim Conrad wrote:
> > Of course, some gullible people actually believe this and compare [2]
> > the existing and working implementations with vaporware (MySQL 5.1,
> > anyone?).
> >
> > > On those same lines, there doesn't seem to be anything about the
> > > improvements in the minor version
On Tue, Apr 27, 2004 at 12:58:59PM -0300, Marc G. Fournier wrote:
> On Tue, 27 Apr 2004, Tim Conrad wrote:
>
> > 2) There doesn't seem to be a clear roadmap on Postgres features.
> >When certian things are expected. There's the TODO list that
> >Bruce maintains, but it only outlines 'near'
On Tue, Apr 27, 2004 at 07:55:08PM +0400, Alexey Borzov wrote:
> Hi!
>
> Tim Conrad wrote:
> >I was researching an article I wrote about a comparison between
> >Postgres and MySQL recently (If you want, you can read the article
> >at http://www.devx.com/dbzone/Article/20743/). I noticed some clear
On Tue, 27 Apr 2004, Tim Conrad wrote:
> 2) There doesn't seem to be a clear roadmap on Postgres features.
>When certian things are expected. There's the TODO list that
>Bruce maintains, but it only outlines 'near' fixes. MySQL has a
>nice listing of what to expect in certian future ve
On Tue, 2004-04-27 at 09:27, Bruce Momjian wrote:
> Here are features that are being worked on, hopefully for 7.5:
>
> o tablespaces (Gavin)
> o nested transactions (Alvaro)
> o two-phase commit (Heikki Linnakangas)
> o integrated pg_autovacuum (O'Connor)
> o PIT
Martin Marques wrote:
> El Tuesday 27 April 2004 10:27, Bruce Momjian escribi?:
> > Here are features that are being worked on, hopefully for 7.5:
> >
> > o tablespaces (Gavin)
> > o nested transactions (Alvaro)
> > o two-phase commit (Heikki Linnakangas)
> > o integrated pg_aut
> > How's Jans' Slowny-I doing? Any chance of getting it at least in the contribs
> > (depending on how stable it gets)?
>
> Zero chance ... Slony-I is *a* replication solution, not *the*
> replication solution ... unless someone ever comes up with an 'end all and
Not to mention Jan doesn't want
I've been sort-of reading this thread off and on, so this may
contain duplicate suggestions.
I was researching an article I wrote about a comparison between
Postgres and MySQL recently (If you want, you can read the article
at http://www.devx.com/dbzone/Article/20743/). I noticed some clear
diffe
On Tuesday 27 April 2004 15:22, Martin Marques wrote:
>
> How's Jans' Slowny-I doing? Any chance of getting it at least in the
> contribs (depending on how stable it gets)?
There was a post from Jan the other day (on General iirc) - I think he's
looking for testers at the moment before he goes to
On Tue, 27 Apr 2004, Martin Marques wrote:
> El Tuesday 27 April 2004 10:27, Bruce Momjian escribió:
> > Here are features that are being worked on, hopefully for 7.5:
> >
> > o tablespaces (Gavin)
> > o nested transactions (Alvaro)
> > o two-phase commit (Heikki Linnakangas)
> >
On Tue, 27 Apr 2004, Richard Huxton wrote:
> Dave Page has bravely stepped into the breach to maintain the ODBC
> driver, but the niggles in it will generate a flood of support messages
> as Windows users test it out. Basically, I'm asking what would need to
> be done technically for the ODBC driv
Hi All,
I've been noticing that files in the pg_clog directory test to stay
around forever, I know they are used to determine the state of
transaction id's, but according to the docs:
"(However, the urgency of this concern has decreased greatly with the
adoption of a segmented storage method f
El Tuesday 27 April 2004 10:27, Bruce Momjian escribió:
> Here are features that are being worked on, hopefully for 7.5:
>
> o tablespaces (Gavin)
> o nested transactions (Alvaro)
> o two-phase commit (Heikki Linnakangas)
> o integrated pg_autovacuum (O'Connor)
> o
On Tuesday 27 April 2004 14:27, Bruce Momjian wrote:
> Here are features that are being worked on, hopefully for 7.5:
>
> o tablespaces (Gavin)
> o nested transactions (Alvaro)
> o two-phase commit (Heikki Linnakangas)
> o integrated pg_autovacuum (O'Connor)
> o P
I think great would be an understatement.
Great work all!
|-+-->
| | Bruce Momjian |
| | <[EMAIL PROTECTED]|
| | > |
| | Sent by: |
|
Here are features that are being worked on, hopefully for 7.5:
o tablespaces (Gavin)
o nested transactions (Alvaro)
o two-phase commit (Heikki Linnakangas)
o integrated pg_autovacuum (O'Connor)
o PITR (Riggs)
o Win32 (Claudio, Magnus)
If we ge
On Mon, 2004-04-26 at 22:04, Alvaro Herrera wrote:
> On Mon, Apr 26, 2004 at 09:36:26PM -0400, Rod Taylor wrote:
> > The function format_type() fails only for interval when used on the
> > interval type
> >
> > template1=# select format_type(oid, typlen) from pg_type;
>
> select format_type(oid,
[EMAIL PROTECTED] wrote:
(5) Programming languages. We need to make a programming language standard
in PostgreSQL. plpgsql is good, but isn't someone working on a Java
language. That would be pretty slick.
IMHO SQL/PSM would be the obvious choice for the standard
procedural language. Not only beca
On Tuesday 27 April 2004 00:32, Bruce Momjian wrote:
> Simon Riggs wrote:
> > On Mon, 2004-04-26 at 23:01, Alvaro Herrera wrote:
> > > On Mon, Apr 26, 2004 at 05:05:41PM -0400, Bruce Momjian wrote:
> > > > I was thinking --- how would someone know the time to use for
> > > > restore?
> > >
> > > I
"Bruce Momjian" <[EMAIL PROTECTED]> wrote in message
> It seems this would be handled just like we handle C functions today,
> that is you create a shared object file, it sits in the file system, and
> you LOAD the object into your backend, or you record it via CREATE
> FUNCTION and specify the pat
On Mon, Apr 26, 2004 at 04:41:35PM -0400, Bruce Momjian wrote:
> Jean-Michel POURE wrote:
> [ PGP not available, raw data follows ]
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > > My question is, "What can we learn from MySQL?" I don't know there is
> > > anything, but I think it
Just a reflection from someone who has not been following PostgreSQL that
long...
I think you provide excellent leadership and keep a firm grip on the core
PostgreSQL server. Moving stuff out to Gborg and the discussion regarding
contrib tells me that you want to keep it that way. As I'm a firm be
Simon Riggs wrote:
Since Phase1 is functioning and should hopefully soon complete, we can
now start thinking about Phase 2: full recovery to a point-in-time.
Previous thinking was that a command line switch would be used to
specify recover to a given point in time, rather than the default, which
wi
80 matches
Mail list logo
