> I and some other developers are also interested in.
> Do you think we can work together?
Sure. Why not. I think it would be practical to decide who is the
leader of this project, though.
--
Tatsuo Ishii
---(end of broadcast)---
TIP 1: subscribe an
There is a website somewhere where a guy posts his patch he is
maintaining that does it. I'll try to find it...
Found it. Check it out:
http://gppl.terminal.ru/index.eng.html
Patch is current for 7.4, Oracle syntax.
Chris
---(end of broadcast)-
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> I and my co workers are very interested in implementing PITR. We will
> tackle this for 7.5 if no one objects.
Sounds good. I'll try to push in the work that Patrick and JR did
within the next day or two, and then you can take it from there...
Andrew Overholt did some work on SQL99 recursive queries, but went back
to university without having gotten to the point where it actually
worked. One of the many things on my to-do list is to pick up and
finish Andrew's work on this. If someone has time to work on it,
let me know and I'll try to
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> Wasn't there some guy at RedHat doing it?
Andrew Overholt did some work on SQL99 recursive queries, but went back
to university without having gotten to the point where it actually
worked. One of the many things on my to-do list is to pick up
I and some other developers are also interested in.
Do you think we can work together?
Tatsuo Ishii <[EMAIL PROTECTED]> wrote:
> > Has this been beaten to death now? Just curious if PITR was in Dev tree
> > yet. Been out of the loop. TIA.
>
> I and my co workers are very interested in implementin
> Has this been beaten to death now? Just curious if PITR was in Dev tree
> yet. Been out of the loop. TIA.
I and my co workers are very interested in implementing PITR. We will
tackle this for 7.5 if no one objects.
--
Tatsuo Ishii
---(end of broadcast)---
I have backed out the background writer sync option. Tom's concerns
where right and my test results have been very questionable.
Jan
--
#==#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break
Is there anyone working on recursive queries for 7.5? I know there is a
patch that implements it on 7.4 (I can't seem to find the guy's
webpage), but that uses Oracle syntax.
Wasn't there some guy at RedHat doing it? Is RedHat working on PITR?
Chris
---(end of broadc
Tom Lane said:
> Andrew Dunstan <[EMAIL PROTECTED]> writes:
>> Right. And if we have sessionids we would want them logged there, I
>> think. And that would rule out anything based on xid or backend pid.
>
> Uh, what's wrong with backend pid? Since we fork before we start doing
> anything with a co
Austin Gonyou <[EMAIL PROTECTED]> writes:
> Has this been beaten to death now? Just curious if PITR was in Dev tree
> yet. Been out of the loop. TIA.
Nope... I've got some patches from Patrick Macdonald and JR Nield that I
need to integrate, but I believe those only cover some low-level changes
to
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Right. And if we have sessionids we would want them logged there, I
> think. And that would rule out anything based on xid or backend pid.
Uh, what's wrong with backend pid? Since we fork before we start doing
anything with a connection, it should su
Paul Ramsey <[EMAIL PROTECTED]> writes:
> I think we had this discussion before though, and the "parameterized"
> types, like varchar(256), were not available for extended types, like
> our geometries.
I can't see any way to handle parameterized types without extending the
grammar individually f
Oops, forgot the patch :)
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
> [EMAIL PROTECTED] On Behalf Of Nicolai Tufar
> Sent: Tuesday, February 03, 2004 9:31 PM
> To: [EMAIL PROTECTED]
> Cc: 'Tom Lane'; [EMAIL PROTECTED]
> Subject: [HACKERS] Turkish Locale in Ident
>Rod Taylor writes
> > > > "scott.marlowe" <[EMAIL PROTECTED]> writes:
> > > > > any chance of having some kind of max_total_sort_mem setting
to
> keep
> > > > > machines out of swap storms, or would that be a nightmare to
> implement?
>
> > Someone asked for this in Copenhagen, and I said we can'
Actually, in my wet dream, we stored everything in system tables.
Dimensionality and SRID became parameters of the geometry, the
selectivity stats lived in the system stats table (as Mark's patch
should hopefully do) and the geometry_columns view just pulled
everything together into one user-co
Has this been beaten to death now? Just curious if PITR was in Dev tree
yet. Been out of the loop. TIA.
--
Austin Gonyou <[EMAIL PROTECTED]>
Coremetrics, Inc.
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Paul Ramsey <[EMAIL PROTECTED]> writes:
> Oh, now I remember. The deal was not views, it was triggers.
Oh, okay. You're right, we don't do triggers on system tables. But
couldn't you combine a view on the system tables with storage of
additional data outside?
regards, to
Try using GiST rtree (examples in contrib), GiST supports multi-key
indexes.
On Tuesday, February 3, 2004, at 06:56 AM, Marcio Caetano wrote:
I'm using PostgreSQL 7.3.2 and I need to create a R-Tree index that
uses more than one column in a table.
When I run the instruction it appears this messa
Try contrib/rtree_gist
Marcio Caetano wrote:
Hello !
I'm using PostgreSQL 7.3.2 and I need to create a R-Tree index that
uses more than one column in a table.
When I run the instruction it appears this message bellow:
DefineIndex: access method "rtree" does not support multi-column
indexes
How c
> Tom Lane <[EMAIL PROTECTED]> wrote:
> "Nicolai Tufar" <[EMAIL PROTECTED]> writes:
> >> A possible compromise is to apply ASCII downcasing (same as in
> >> keywords.c) for 7-bit-ASCII characters, and apply tolower() only
> >> for character codes above 127. In other words
>
> > If we go this way
Bitter experience... I am going to cc Dave here, because I could swear
we went through many conniptions trying to make this work.
And yet I just did this:
create view mytables as select relname from pg_class where relam = 0
and relname not like 'pg_%';
And it seems to work fine.
Oh, now I rem
> > > "scott.marlowe" <[EMAIL PROTECTED]> writes:
> > > > any chance of having some kind of max_total_sort_mem setting to keep
> > > > machines out of swap storms, or would that be a nightmare to implement?
> Someone asked for this in Copenhagen, and I said we can't see how to do
> it. The only
Hello !
I'm using PostgreSQL 7.3.2 and I need to create a R-Tree index that
uses more than one column in a table.
When I run the instruction it appears this message bellow:
DefineIndex: access method "rtree" does not support multi-column
indexes
How can I solve this problem ?
Is it a limitati
Paul Ramsey <[EMAIL PROTECTED]> writes:
> In an idea world though, we would construct the thing as a view, so
> that when you did a CREATE TABLE that included a geometry type, you
> would automatically get a row in geometry_columns. That requires a view
> on system tables though, and that just d
One of the great annoyances of the OpenGIS spec is the requirement for
a "geometry_columns" table, that has a list of all the spatial columns
and a little bit of metadata on them (what type are they, what is the
spatial reference system of their coordinates, what is their
dimensionality).
Unfo
Tom Lane wrote:
Bruce Momjian <[EMAIL PROTECTED]> writes:
Andrew Dunstan wrote:
Bruce and others have suggested that PID is not sufficiently unique.
The nice things about using xid for session id is that is is unique for
a long time, rather than pid.
Hmm. Now that I think
Hi Augusto,
> How can I configure postgreSQL to search without acents?
> Is PostgreSQL have this support?
>
There isn't a specific function in postgresql. Maybe you could implement it in PL/Perl
or any other PL/* language.
> SELECT * FROM test WHERE name LIKE _tes%_
>
> And it should return va
Bruce Momjian <[EMAIL PROTECTED]> writes:
> If people want this, can I get some wording?
* Make pg_restore continue after errors, so it acts more like pg_dump scripts
regards, tom lane
---(end of broadcast)---
TIP 1: subscri
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Andrew Dunstan wrote:
>> Bruce and others have suggested that PID is not sufficiently unique.
> The nice things about using xid for session id is that is is unique for
> a long time, rather than pid.
Hmm. Now that I think about it, InitPostgres() alwa
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > If people want this, can I get some wording?
>
> * Make pg_restore continue after errors, so it acts more like pg_dump scripts
Added.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED]
Tom Lane wrote:
Shutdown of an idle postmaster used to take about two or three seconds
(mostly due to the sync/sleep(2)/sync in md_sync). For the last couple
of days it's taking more like a dozen seconds. I presume somebody broke
something, but I'm unsure whether to pin the blame on bgwriter or
--On Tuesday, February 03, 2004 11:12:03 -0500 Andrew Dunstan
<[EMAIL PROTECTED]> wrote:
Peter Eisentraut wrote:
Andrew Dunstan wrote:
I am less sure of the utility of such an ID, though. After all, if
you see a disconnect log message for a given PID you must know that
any reuse of that PI
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> I didn't think there was. just hoping... :-)
> Someone asked for this in Copenhagen, and I said we can't see how to do
> it. The only idea I had as to give the first requestor 50% of the
> total, then a second query 50% of the remaining memory. Is th
Fabien COELHO wrote:
>
> > Fabien COELHO <[EMAIL PROTECTED]> writes:
> > > It would make sense to ignore some alter/drop errors in pg_restore.
> >
> > [...]
> >
> > This issue has been on the radar screen for awhile, but no one has
> > gotten around to making it happen...
>
> Maybe it could be ap
Andrew Dunstan wrote:
> Tom Lane said:
> > Andrew Dunstan <[EMAIL PROTECTED]> writes:
> >> I'm not sure I understand. I didn't suggest that a sequence should be
> >> used for txn ids. For the purpose I had in mind we would call
> >> nextval() once per connection,
> >
> > Oh, okay, I misunderstood.
scott.marlowe wrote:
> On Mon, 2 Feb 2004, Tom Lane wrote:
>
> > "scott.marlowe" <[EMAIL PROTECTED]> writes:
> > > any chance of having some kind of max_total_sort_mem setting to keep
> > > machines out of swap storms, or would that be a nightmare to implement?
> >
> > I don't see any reasonable
Peter Eisentraut wrote:
Andrew Dunstan wrote:
I am less sure of the utility of such an ID, though. After all, if
you see a disconnect log message for a given PID you must know that
any reuse of that PID indicates a new session, or even if you just
see a connection message you know it must be
Andrew Dunstan wrote:
> I am less sure of the utility of such an ID, though. After all, if
> you see a disconnect log message for a given PID you must know that
> any reuse of that PID indicates a new session, or even if you just
> see a connection message you know it must be a new session. OTOH,
>
Tom Lane said:
> Andrew Dunstan <[EMAIL PROTECTED]> writes:
>> I'm not sure I understand. I didn't suggest that a sequence should be
>> used for txn ids. For the purpose I had in mind we would call
>> nextval() once per connection,
>
> Oh, okay, I misunderstood. But why not just use the PID?
>
B
Kevin Brown <[EMAIL PROTECTED]> writes:
> Slavisa Garic wrote:
>> Using pg module in python I am trying to run the COPY command to populate
>> the large table. I am using this to replace the INSERT which takes about
>> few hours to add 7 entries where copy takes minute and a half.
> That diff
Kevin Brown <[EMAIL PROTECTED]> writes:
> Instead, have each backend maintain its own separate list in shared
> memory. The only readers of a given list would be the backend it belongs
> to and the bgwriter, and the only time bgwriter attempts to read the
> list is at checkpoint time.
> The sum t
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> I'm not sure I understand. I didn't suggest that a sequence should be
> used for txn ids. For the purpose I had in mind we would call nextval()
> once per connection,
Oh, okay, I misunderstood. But why not just use the PID?
r
> >
> > Tom Lane wrote:
> >
> >> Andrew Dunstan <[EMAIL PROTECTED]> writes:
> >>
> >>> I did think about using a cluster-wide sequence, if we can make such
> >>> a thing (might also be useful for system generated UIDs too).
> >>
> >> Not a good idea IMHO. If you do that, then there will be no suc
> Fabien COELHO <[EMAIL PROTECTED]> writes:
> > It would make sense to ignore some alter/drop errors in pg_restore.
>
> [...]
>
> This issue has been on the radar screen for awhile, but no one has
> gotten around to making it happen...
Maybe it could be appended to the "todo" list, so as not to b
[note change of subject]
I wrote:
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
I did think about using a cluster-wide sequence, if we can make such
a thing (might also be useful for system generated UIDs too).
Not a good idea IMHO. If you do that, then there will be no su
Slavisa Garic wrote:
> Using pg module in python I am trying to run the COPY command to populate
> the large table. I am using this to replace the INSERT which takes about
> few hours to add 7 entries where copy takes minute and a half.
That difference in speed seems quite large. Too large.
Some Moron at sysexperts.com wrote:
> At checkpoint time, for each backend list, the bgwriter grabs a write
> lock on the list, copies it into its own memory space, truncates the
> list, and then releases the read lock.
Sigh. I meant to say that it then releases the *write* lock.
--
Kevin Brow
Bruce Momjian wrote:
> Here is my new idea. (I will keep throwing out ideas until I hit on a
> good one.) The bgwriter it going to have to check before every write to
> determine if the file is already recorded as needing fsync during
> checkpoint. My idea is to have that checking happen during
49 matches
Mail list logo
