Sorry for sending this directly to the hackers mailing list. But, i think it
did not belong in any other as it involves internals about the files in the
data directory.
PostgreSQL version: 8.1.2
Operating system: Windows XP/2003
The PostgreSQL service is not starting anymore. When I manually
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 3 Mar 2008 20:33:08 -0500 (EST)
Bruce Momjian <[EMAIL PROTECTED]> wrote:
> Added to TODO based on this discussion:
>
> o Allow pg_dump to utilize multiple CPUs and I/O channels by
> dumping multiple objects simultaneously
>
>
A quick recap: I submitted a patch for empty ARRAY[] syntax back in
November, and as far as I can see it never made it to the patches
list. Gregory suggested a different way of approaching the problem
(quoted below), but nobody commented further about how it might be
made to work.
I'd like to RFC
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Added to TODO based on this discussion:
>
> > o To better utilize resources, restore data, primary keys, and
> > indexes for a single table before restoring the next table
>
> That idea seems quite misguided, and ce
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Added to TODO based on this discussion:
> o To better utilize resources, restore data, primary keys, and
> indexes for a single table before restoring the next table
That idea seems quite misguided, and certainly was not anywhere in th
Heikki, are there any TODO items here?
---
Heikki Linnakangas wrote:
> Joshua D. Drake wrote:
> > On Sun, 24 Feb 2008 00:43:18 +
> > "Heikki Linnakangas" <[EMAIL PROTECTED]> wrote:
> >
> >> Incidentally, I've been work
Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > I've not been advocating improving pg_restore, which is where the -Fc
> > tricks come in.
> > ...
> > I see you thought I meant pg_restore. I don't thinking extending
> > pg_restore in that way is of sufficiently generic use to make it
>
Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > So if I understand:
>
> > * we add switches to pg_dump to dump out separate files with --pre,
> > --post and --data (or other names) [TODO: Simon]
>
> > * we add switches to pg_restore to load/dump from the single archive
> > file the
Decibel! wrote:
> On Feb 26, 2008, at 4:36 PM, Tom Lane wrote:
> > I think a sane way to think about what Simon would like to accomplish
> > is not "turn psql into a parallel job scheduler"
>
>
> My $0.02: I often find myself wishing I could perform parallel
> operations in psql. There was a pr
On Mon, Mar 3, 2008 at 8:46 AM, Heikki Linnakangas
<[EMAIL PROTECTED]> wrote:
> Tom Lane wrote:
> > Do you want to write up a flag-based patch, or shall I?
>
> I can do that.
BTW, I found a easier way of reproducing this (see attached 2pc.sql).
It might help with debugging or verifying a fix/reg
Josh Berkus wrote:
Stefan,
http://developer.postgresql.org/index.php/Todo:PatchStatus
that one is in serious need of some updating which I have not found any
time for lately :-(
Right. I'll happily update it if Bruce will supply me the raw data.
My time right now is l
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> I'm seeing a 8.3 database whose autovacuum-initiated vacuums are being
> cancelled and I am not sure of the cause. I am wondering if a HOT
> cleanup round on a page could try to acquire locks on it that would
> conflict with autovacuum (basically anythi
=?UTF-8?B?SmFuIFVyYmHFhHNraQ==?= <[EMAIL PROTECTED]> writes:
> 2. Implement better selectivity estimates for FTS.
+1 for that one ...
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your Subscription:
http://mail.
Stefan,
> > http://developer.postgresql.org/index.php/Todo:PatchStatus
>
> that one is in serious need of some updating which I have not found any
> time for lately :-(
Right. I'll happily update it if Bruce will supply me the raw data.
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
--
Joshua D. Drake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 3 Mar 2008 13:55:51 -0800
Josh Berkus <[EMAIL PROTECTED]> wrote:
Tom, Bruce,
Is there a list somewhere of the patches submitted for the first
commit fest? I'd like to wiki-ize them so we can all spectate and
take be
Josh Berkus wrote:
> Tom, Bruce,
>
> Is there a list somewhere of the patches submitted for the first commit
> fest? I'd like to wiki-ize them so we can all spectate and take bets.
No, I am still going through the stuff from last week and have not
started on the patches_hold emails yet.
--
Following the discussion on making UUID data type to be much more liberal
( http://archives.postgresql.org/pgsql-hackers/2008-02/msg01214.php )
I have decided to try to approach it from more general perspective.
The current state of code is available at:
http://qnex.net/hexstring-0.1-2008-03-03.tg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 3 Mar 2008 13:55:51 -0800
Josh Berkus <[EMAIL PROTECTED]> wrote:
> Tom, Bruce,
>
> Is there a list somewhere of the patches submitted for the first
> commit fest? I'd like to wiki-ize them so we can all spectate and
> take bets.
>
http://d
Tom, Bruce,
Is there a list somewhere of the patches submitted for the first commit
fest? I'd like to wiki-ize them so we can all spectate and take bets.
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
Added to TODO:
* Allow INSERT ... DELETE ... RETURNING, namely allow the DELETE ...
RETURNING to supply values to the INSERT
http://archives.postgresql.org/pgsql-hackers/2008-02/thrd2.php#00979
---
Jonah H. Harris wrote
The latest version of libpq type system is available here:
http://www.esilo.com/projects/postgresql/libpq/typesys-0.9a.tar.gz
The following modifications where made:
*) documentation fixes
*) parameter resets are no longer automatic
*) updated to patch vs. REL8_3_STABLE
Merlin Moncure & Andrew Ch
Hi,
I'm seeing a 8.3 database whose autovacuum-initiated vacuums are being
cancelled and I am not sure of the cause. I am wondering if a HOT
cleanup round on a page could try to acquire locks on it that would
conflict with autovacuum (basically anything that conflicts with a
vacuum lock). This w
Pavel Stehule wrote:
> Hello
>
> I have to write this patch first. I am waiting for apply EXECUTE USING
> patch and others plpgsql patches.
OK, removed. Thanks.
---
>
> Regards
> Pavel Stehule
>
> On 03/03/2008, Bruce M
On Thu, Feb 28, 2008 at 10:23 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> Don't forget that our first "commit fest" for 8.4 development starts
> Saturday March 1. If you've got a patch that you'd like reviewed in
> this fest, it's time to send it in. (But there's plenty more fests
> to come, so
Hello
I have to write this patch first. I am waiting for apply EXECUTE USING
patch and others plpgsql patches.
Regards
Pavel Stehule
On 03/03/2008, Bruce Momjian <[EMAIL PROTECTED]> wrote:
>
> Your patch has been added to the PostgreSQL unapplied patches list at:
>
> http://momjian.post
Hi PostgreSQL!
Although this year's GSoC is just starting, I thought getting in touch a bit
earlier would only be of benefit.
I study Computer Science in Faculty of Mathematics, Informatics
and Mechanics of Warsaw University. I'm currently in my fourth year of
studies. Having chosen Databases fo
Tom Lane wrote:
Do you want to write up a flag-based patch, or shall I?
I can do that.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your Subscription:
http://mail.postgresql.org/mj
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
It will be applied as soon as one of the PostgreSQL committers reviews
and approves it.
---
Pa
I certainly would be interested to see if it improves performance.
---
Simon Riggs wrote:
> In Read Committed transactions we take snapshots much more frequently
> than transactions begin and commit. It would be help scalabi
Added to TODO:
* Allow the UUID type to accept non-standard formats
http://archives.postgresql.org/pgsql-hackers/2008-02/msg01214.php
---
Dawid Kuroczko wrote:
> Hello.
>
> I am currently playin
Florian G. Pflug wrote:
> Greg Stark wrote:
> > Florian G. Pflug wrote:
> >> The same holds true for index scans, though. Maybe we can find a
> >> solution that benefits both cases - something along the line of a
> >> bgreader process
> > I posted a patch to do readahead for bitmap index scans us
I have added the following TODO:
* Speed WAL recovery by allowing more than one page to be prefetched
This involves having a separate process that can be told which pages
the recovery process will need in the near future.
http://archives.post
Sorry!
As rightly pointed out, guess I should have posted this to pgadmin-hackers
instead.
*Robins Tharakan*
On Mon, Mar 3, 2008 at 11:19 PM, Robins Tharakan <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I read about Google Summer of Code recently and being involved with
> pgAdmin since a few weeks, woul
Hi,
I read about Google Summer of Code recently and being involved with pgAdmin
since a few weeks, would like to add the Query Builder feature to pgAdmin,
as a part of this programme.
I have been reading GSoC related emails in the past year on various PG
lists, and believe that keeping a project
"Heikki Linnakangas" <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Actually ... why are we using the lock manager to drive this at all?
> Good question. It has always seemed a bit strange to me. The assumption
> that we always hold the lock on temp table until end of transaction,
> while true
Reminder to patch appliers,
If you apply a patch that was discussed on patches or hackers, please
reply to the email indicating you have applied the patch. I can connect
the commit message to the email discussion but often the patch submitter
does not read committers so it would be good for them
Alvaro Herrera wrote:
Heikki Linnakangas escribió:
In the future, it would be nice to relax the restriction on using temp
rels, though. A flag doesn't lend itself to that easily, but I'm sure
we'll figure out something if we ever get around to implement that.
I can't recall the rationale f
Heikki Linnakangas escribió:
> In the future, it would be nice to relax the restriction on using temp
> rels, though. A flag doesn't lend itself to that easily, but I'm sure
> we'll figure out something if we ever get around to implement that.
I can't recall the rationale for this limitation.
Aidan Van Dyk wrote:
How difficult is it to parse the WAL logs with enough knowledge to know
what heap page (file/offset) a wal record contains (I haven't looked
into any wal code)?
Unfortunately there's no common format for that. All the heap-related
WAL records, insert, update and delete, ha
Tom Lane wrote:
I wrote:
I think we need some better means of recording whether a lock is on a
temp object. We could certainly add a flag to the LOCALLOCK struct,
but it's not clear where a clean place to set it would be. As a rule
we don't yet know when locking a relation whether it's temp or
40 matches
Mail list logo
