On Sat, 24 Feb 2007, Warren Turkal wrote:
> On Saturday 24 February 2007 00:32, Jeremy Drake wrote:
> > Use cvsup, or if you don't want to go through the effort of getting that
> > set up, use rsync:
> >
> > rsync -avzCH --delete rsync.postgresql.org::pgsql-cvs cvsroot/
>
> Thanks for this. Is thi
Warren Turkal wrote:
> On Friday 23 February 2007 17:30, Gregory Stark wrote:
>> The distributed systems sound neat and do sound like they match our style
>> of working. But they seem like a big leap for a project that's still using
>> a buggy unmaintained pile of spaghetti code for fear of change.
On Wednesday 21 February 2007 21:23, Warren Turkal wrote:
> Are there any plans to move to another SCMS in the future? I am curious, I
> guess.
Is it possible to obtain a mirror of the CVS repository? The version of CVS on
the repository server is incompatible with cvsps (at least the version on
On Saturday 24 February 2007 00:32, Jeremy Drake wrote:
> Use cvsup, or if you don't want to go through the effort of getting that
> set up, use rsync:
>
> rsync -avzCH --delete rsync.postgresql.org::pgsql-cvs cvsroot/
Thanks for this. Is this documented somewhere that I should have looked?
wt
--
On Friday 23 February 2007 23:10, Alvaro Herrera wrote:
> To be frank, I don't like Git's data model. Git has always seemed
> much too complex to use to me. I have more than enough with a single
> distributed SCM.
Have you ever tried cogito or any of the other apps for interacting with a git
re
On Sat, 24 Feb 2007, Warren Turkal wrote:
> The interesting thing about Git is that is has two way sync support for a SVN
> repository also. You could run a Git repository pushing changes in real time
> to a SVN repository and present a CVS frontend also. I would like to try
> converting the CVS r
On Friday 23 February 2007 12:03, Andrew Hammond wrote:
> While annoying, this is something that really only a problem for the
> CVS maintainer (and anyone who's stuck waiting for the maintainer to
> shuffle stuff). I suggest that while it would be nice to solve this
> problem, it's more of a bonus
On Friday 23 February 2007 17:30, Gregory Stark wrote:
> The distributed systems sound neat and do sound like they match our style
> of working. But they seem like a big leap for a project that's still using
> a buggy unmaintained pile of spaghetti code for fear of change. Subversion
> is the path
Joshua D. Drake wrote:
> Magnus Hagander: VC++ support (thank goodness)
I would much appreciate more people testing and commenting on this one,
from the version in CVS head.
//Magnus
---(end of broadcast)---
TIP 3: Have you checked our extensi
Warren Turkal wrote:
> On Friday 23 February 2007 08:30, Alvaro Herrera wrote:
> > Sorry, I mean Windows. We're taken pains to ensure Postgres runs on
> > Windows, we're not going to abandon that platform now.
>
> This is why I would propose the use of the CVS gateway on top of git. Also,
> Wiki
"Florian G. Pflug" <[EMAIL PROTECTED]> writes:
> My line of reasoning is that stopping wal replay at a arbitrary point,
> and then starting a read-only transaction with an "empty snapshot" (meaning
> that all exactly those transactions marked as comitted in the clog are
> assumed to be visible to
On Friday 23 February 2007 08:30, Alvaro Herrera wrote:
> Sorry, I mean Windows. We're taken pains to ensure Postgres runs on
> Windows, we're not going to abandon that platform now.
This is why I would propose the use of the CVS gateway on top of git. Also,
Wikipedia claims there is a MingW32 p
On 2/23/07, Tom Lane <[EMAIL PROTECTED]> wrote:
"Merlin Moncure" <[EMAIL PROTECTED]> writes:
> On friday we upgraded a critical backend server to postgresql 8.2
> running on fedora core 4.
Umm ... why that particular choice of OS? Red Hat dropped update
support for FC4 some time ago, and AFAIK
Josh Berkus wrote:
People weren't very interested in having a read-only mode. I think it
would be a nice feature if it's not too complicated.
Actually, I think there's high demand for it off this list. Effectively it
would allow our "warm backup mode" to become a "hot backup mode". As SoC
Gregory Stark wrote:
"Tom Lane" <[EMAIL PROTECTED]> writes:
I note also that CVS does have the ability to merge changes across
branches, we just choose not to use it that way.
And the reason why, I assume, is because it's hard to grant access to CVS
without granting access to do anythi
Heikki Linnakangas wrote:
Florian G. Pflug wrote:
I plan to submit a proposal for implementing support for
read-only queries during wal replay as a "Google Summer of Code 2007"
project.
I've been browsing the postgres source-code for the last few days,
and came up with the following plan for a
"Gregory Stark" <[EMAIL PROTECTED]> writes:
> "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
>
>> Greg Stark: WITH/Recursive Queries?
>
> Uhm, I posted two weeks ago saying I had to shelve that temporarily.
>
> On the other hand I've submitted a patch to reduce the storage overhead of
> varlenas u
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
>> Yes, it's nice. Consider this: Andrew develops some changes to PL/perl
>> in his branch. Neil doesn't like something in those changes, so he
>> commits a fix there. In the meantime, Tom has been busy with hi
On Fri, Feb 23, 2007 at 06:47:52PM -0500, Tom Lane wrote:
> I wrote:
> > I don't find this particularly important, because we have never intended
> > direct update of catalog entries to be a primary way of interacting with
> > the system. The current pg_autovacuum setup is a stopgap until the dust
On Fri, Feb 23, 2007 at 04:24:29PM -0700, Warren Turkal wrote:
> On Friday 23 February 2007 15:50, you wrote:
> > How to people get a branch? Do they have their own logins?
>
> If monotone is something like Git, you just create it in your local working
> copy and push is somewhere public when yo
>
> Looks like we are doing redundant work here:
> http://developer.postgresql.org/index.php/Todo:WishlistFor83
>
> Where/how do you maintained your todo list Joshua? Would love to join
> "forces" on this one .. especially since I send out emails to many of
> the above noted people. If we both
Alvaro Herrera wrote:
> Yes, it's nice. Consider this: Andrew develops some changes to PL/perl
> in his branch. Neil doesn't like something in those changes, so he
> commits a fix there.
If I understand right, another advantage is that the SCM will keep
track of which of those changes came fr
Joshua D. Drake wrote:
Hello,
5 weeks to feature freeze folks. Please provide updates including if you
think you will have a patch submitted before feature freeze. Be
realistic, if you can't make it -- say so.
Alvaro Herrera: Autovacuum improvements (maintenance window etc..)
Gavin Sherry: Bit
I wrote:
> I don't find this particularly important, because we have never intended
> direct update of catalog entries to be a primary way of interacting with
> the system. The current pg_autovacuum setup is a stopgap until the dust
> has settled enough that we know what sort of long-term API we w
On Friday 23 February 2007 00:55, Lukas Kahwe Smith wrote:
> Anyone who followed the thread willing to list the mentioned
> requirements as well as the pro's and con's of the differnent options in
> the developer wiki [1]?
Does the dev wiki even have a link from the site? I can't find a link under
Bruce Momjian wrote:
Lukas Kahwe Smith wrote:
Simon Riggs wrote:
If this is standards-breaking as you say, I would withdraw immediately.
I checked the SQL standard and could not see how this would do so. The
standard states SELECT * would return columns in order; it doesn't say
what that order
* Bruce Momjian:
>> The fact that you're still thinking in "patch application" means you're
>> still stuck in the CVS worldview. To "apply a patch" in a distributed
>> SCM(*) really means to merge a branch into the main development branch.
>> Of course, you can still see the entire "diff -c" if y
Also, I have several heavy patches in the patch queue that I am not
comfortable reviewing/applying:
http://momjian.postgresql.org/cgi-bin/pgpatches
---
Joshua D. Drake wrote:
> Hello,
>
> 5 weeks to feature freeze
On Fri, Feb 23, 2007 at 10:57:24PM +, Heikki Linnakangas wrote:
> Florian G. Pflug wrote:
> >I plan to submit a proposal for implementing support for
> >read-only queries during wal replay as a "Google Summer of Code 2007"
> >project.
> >
> >I've been browsing the postgres source-code for the l
On Friday 23 February 2007 15:50, you wrote:
> How to people get a branch? Do they have their own logins?
If monotone is something like Git, you just create it in your local working
copy and push is somewhere public when you are ready, or you can just
generate the changeset and submit that.
wt
Bruce Momjian wrote:
> Joshua D. Drake wrote:
>> Bruce Momjian wrote:
>>> Peter Eisentraut wrote:
Bruce Momjian wrote:
> Log Message:
> ---
> Update Solaris FAQ.
Could someone please translate this to English first?
>>> Updated text:
>>>
>>> 9) Can I compile PostgreSQL
Joshua D. Drake wrote:
> Bruce Momjian wrote:
> > Peter Eisentraut wrote:
> >> Bruce Momjian wrote:
> >>> Log Message:
> >>> ---
> >>> Update Solaris FAQ.
> >> Could someone please translate this to English first?
> >
> > Updated text:
> >
> > 9) Can I compile PostgreSQL with Kerberos v5
"Merlin Moncure" <[EMAIL PROTECTED]> writes:
> On friday we upgraded a critical backend server to postgresql 8.2
> running on fedora core 4.
Umm ... why that particular choice of OS? Red Hat dropped update
support for FC4 some time ago, and AFAIK the Fedora Legacy project
is not getting things do
Josh Berkus wrote:
>> People weren't very interested in having a read-only mode. I think it
>> would be a nice feature if it's not too complicated.
>
> Actually, I think there's high demand for it off this list. Effectively it
> would allow our "warm backup mode" to become a "hot backup mode".
> People weren't very interested in having a read-only mode. I think it
> would be a nice feature if it's not too complicated.
Actually, I think there's high demand for it off this list. Effectively it
would allow our "warm backup mode" to become a "hot backup mode". As SoC
admin, I'd vote f
I'll throw in my vote, I would find this quite useful.
-Glen
Florian G. Pflug wrote:
I plan to submit a proposal for implementing support for
read-only queries during wal replay as a "Google Summer of Code 2007"
project.
I've been browsing the postgres source-code for the last few days,
and c
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Yes, it's nice. Consider this: Andrew develops some changes to PL/perl
> in his branch. Neil doesn't like something in those changes, so he
> commits a fix there. In the meantime, Tom has been busy with his own
> stuff and committing to the main branc
Florian G. Pflug wrote:
I plan to submit a proposal for implementing support for
read-only queries during wal replay as a "Google Summer of Code 2007"
project.
I've been browsing the postgres source-code for the last few days,
and came up with the following plan for a implementation.
I'd be ver
Alvaro Herrera wrote:
> Bruce Momjian wrote:
>
> > My typical cycle is to take the patch, apply it to my tree, then cvs
> > diff and look at the diff, adjust the source, and rerun until I like the
> > diff and apply. How do I do that with this setup?
>
> The same, except that you don't need to t
Bruce Momjian wrote:
> My typical cycle is to take the patch, apply it to my tree, then cvs
> diff and look at the diff, adjust the source, and rerun until I like the
> diff and apply. How do I do that with this setup?
The same, except that you don't need to take the patch out of an email
and in
Jeff,
> I am still on target. I'm scheduling some benchmarks on real hardware
> and real queries in the next week or two. If those show the results I
> expect, I'll be ready before feature freeze.
Send me a patch against 8.2.3 and I'll pass it to the Sun benchmarking
team.
--
--Josh
Josh Berk
On Fri, 2007-02-23 at 17:14 -0500, Merlin Moncure wrote:
> BUG: spinlock recursion CPU0 postmaster...not tainted.
> Has anybody seen any problem like this or have any suggestions about
> possible resolution...should I be posting to the LKML?
AFAIR (+ some quick Googling), this is related to
On Fri, 2007-02-23 at 13:24 -0800, Joshua D. Drake wrote:
> Jeff Davis: Synchronized scanning
I am still on target. I'm scheduling some benchmarks on real hardware
and real queries in the next week or two. If those show the results I
expect, I'll be ready before feature freeze.
Regards,
J
Bruce Momjian wrote:
>
> My typical cycle is to take the patch, apply it to my tree, then cvs
> diff and look at the diff, adjust the source, and rerun until I like the
> diff and apply. How do I do that with this setup?
The most similar to what you're doing would be to
merge the patch's branch
Lukas Kahwe Smith wrote:
> Simon Riggs wrote:
>
> > If this is standards-breaking as you say, I would withdraw immediately.
> > I checked the SQL standard and could not see how this would do so. The
> > standard states SELECT * would return columns in order; it doesn't say
> > what that order shou
Ok,
This may the wrong place to look for answers to this, but I figured it
couldn't hurt...so here goes:
On friday we upgraded a critical backend server to postgresql 8.2
running on fedora core 4. Since then we have received three kernel
panics during periods of moderate to high load (twice dur
"Florian G. Pflug" <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> You are discussing this on the wrong list.
> So what list would be more appropriate?
My mistake, I read the message header and saw "Postgresql-General" ...
did not look at the actual address ...
regards,
Gregory Stark wrote:
> "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
>
>> Greg Stark: WITH/Recursive Queries?
>
> Uhm, I posted two weeks ago saying I had to shelve that temporarily.
I can't read every email :)
Can someone pick this up? This would be the second time that this has
been dropped.
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> Greg Stark: WITH/Recursive Queries?
Uhm, I posted two weeks ago saying I had to shelve that temporarily.
On the other hand I've submitted a patch to reduce the storage overhead of
varlenas under 128 bytes by 3-7 bytes each.
--
Gregory Stark
Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > Alvaro Herrera wrote:
> > > Bruce Momjian wrote:
> > > > Gregory Stark wrote:
> > > > > You're still merging patches and reviewing patches by hand, without
> > > > > any of the
> > > > > tools to, for example, view incremental changes in the branch,
Bruce Momjian wrote:
> Alvaro Herrera wrote:
> > Bruce Momjian wrote:
> > > Gregory Stark wrote:
> > > > You're still merging patches and reviewing patches by hand, without any
> > > > of the
> > > > tools to, for example, view incremental changes in the branch, view the
> > > > logs
> > > > of t
> The only thing I can think of is to remove the support for ancient COPY
> syntax from psql's \copy, as suggested here:
> http://archives.postgresql.org/pgsql-hackers/2007-02/msg01078.php
>
> That's hardly a feature - more a matter of tidying up.
I thought you were being sponsored for something
>>
>> Neil Conway: pgmemcache
>> Josh Drake: pgmemcache
>>
>
>
> what does this refer to?
Neil is cleaning up the code, I am cleaning up the docs.
Joshua D. Drake
>
>
> cheers
>
> andrew
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564
Joshua D. Drake wrote:
Andrew Dunstan: Something with COPY? Andrew?
The only thing I can think of is to remove the support for ancient COPY
syntax from psql's \copy, as suggested here:
http://archives.postgresql.org/pgsql-hackers/2007-02/msg01078.php
That's hardly a feature - more a mat
Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > Gregory Stark wrote:
> > > You're still merging patches and reviewing patches by hand, without any
> > > of the
> > > tools to, for example, view incremental changes in the branch, view the
> > > logs
> > > of the branch, merge the branch into the
Hello,
5 weeks to feature freeze folks. Please provide updates including if you
think you will have a patch submitted before feature freeze. Be
realistic, if you can't make it -- say so.
Alvaro Herrera: Autovacuum improvements (maintenance window etc..)
Gavin Sherry: Bitmap Indexes (on disk), po
Bruce Momjian wrote:
> Gregory Stark wrote:
> > You're still merging patches and reviewing patches by hand, without any of
> > the
> > tools to, for example, view incremental changes in the branch, view the logs
> > of the branch, merge the branch into the code automatically taking into
> > accoun
Bruce Momjian wrote:
> Peter Eisentraut wrote:
>> Bruce Momjian wrote:
>>> Log Message:
>>> ---
>>> Update Solaris FAQ.
>> Could someone please translate this to English first?
>
> Updated text:
>
> 9) Can I compile PostgreSQL with Kerberos v5 support?
>
> Kerberos is integrated in OpenS
Peter Eisentraut wrote:
> Bruce Momjian wrote:
> > Log Message:
> > ---
> > Update Solaris FAQ.
>
> Could someone please translate this to English first?
Updated text:
9) Can I compile PostgreSQL with Kerberos v5 support?
Kerberos is integrated in OpenSolaris and will be integrated in S
Gregory Stark wrote:
> You're still merging patches and reviewing patches by hand, without any of the
> tools to, for example, view incremental changes in the branch, view the logs
> of the branch, merge the branch into the code automatically taking into
> account the known common ancestor. Instead
Bruce Momjian wrote:
> Log Message:
> ---
> Update Solaris FAQ.
Could someone please translate this to English first?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 1: if posting/reading through U
On Feb 22, 9:49 am, [EMAIL PROTECTED] (Alvaro Herrera) wrote:
> Andrew Dunstan wrote:
> > It's also fair to say that this is a subject about which we usually get
> > much more noise from partisans of other SCM systems than from the
> > relatively small number of people who actually have to maintain
Martijn van Oosterhout wrote:
> On Fri, Feb 23, 2007 at 09:12:27AM -0500, Chris Browne wrote:
>> It looks as though there is a strong "plurality" of PostgreSQL
>> developers that are waiting for some alternative to become dominant.
>> I suspect THAT will never happen.
Actually it has. The problem
Tom Lane wrote:
"Florian G. Pflug" <[EMAIL PROTECTED]> writes:
I plan to submit a proposal for implementing support for
read-only queries during wal replay as a "Google Summer of Code 2007"
project.
You are discussing this on the wrong list.
So what list would be more appropriate?
B) Split
On Feb 23, 2007, at 11:24 , Andreas Pflug wrote:
It probably _can_ never happen, because that would have to be a
one-for-all solution, embracing both centric and distributed
repositories, combining contradictionary goals. So the first
question to
answer is: Will PostgreSQL continue with a
On Fri, Feb 23, 2007 at 08:32:34AM -0800, Joshua D. Drake wrote:
> I am happy to help with this any way I can, because I would love to see
> CVS take a big diving leap off the backend of mysql into the truncated
> data set of hell.
That quote made the whole argument coming up again worthwhile. :)
On Fri, Feb 23, 2007 at 09:12:27AM -0500, Chris Browne wrote:
> It looks as though there is a strong "plurality" of PostgreSQL
> developers that are waiting for some alternative to become dominant.
> I suspect THAT will never happen.
Actually, I think that if one of the SCMs provides some kind of
First, it would absolutely be best if we just got the full blown patch
into 8.3 and were done with it. I don't think anyone's arguing against
that... it's a question of what we can do if that can't happen (and it
does sound like the patch lost it's maintainer when the direction
changed towards doin
On Fri, Feb 23, 2007 at 01:22:17PM -0300, Alvaro Herrera wrote:
> Jim C. Nasby wrote:
> > On Thu, Feb 22, 2007 at 10:32:44PM -0500, Matthew T. O'Connor wrote:
>
> > > I'm not sure this is a great idea, but I don't see how this would result
> > > in large numbers of workers working in one database
"Florian G. Pflug" <[EMAIL PROTECTED]> writes:
> I plan to submit a proposal for implementing support for
> read-only queries during wal replay as a "Google Summer of Code 2007"
> project.
You are discussing this on the wrong list.
> B) Split StartupXLOG into two steps. The first (Recovery) will
Hi,
Here's some feedback, this is a feature that would be very useful to a
project I am currently working on.
Doug
On Fri, 2007-02-23 at 17:34 +0100, Florian G. Pflug wrote:
> Hi
>
> I plan to submit a proposal for implementing support for
> read-only queries during wal replay as a "Google Summ
Joshua D. Drake wrote:
Moreover work on things like bitmapped indexes that other people want to help
on is hampered by this need to be mailing around patches. If two or three
people submit changes (based possibly on different old versions of the patch)
the main developer has to merge them into hi
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Osprey is a NetBSD running on m68k
Yeah, it's been failing consistently on the 8.2 branch for a while, but
not either 8.1 or HEAD, which is awfully strange.
> Program terminated with signal 11, Segmentation fault.
> #0 0x001f74d6 in AllocSetAlloc (con
Hi
I plan to submit a proposal for implementing support for
read-only queries during wal replay as a "Google Summer of Code 2007"
project.
I've been browsing the postgres source-code for the last few days,
and came up with the following plan for a implementation.
I'd be very interested in any f
On Wed, Feb 21, 2007 at 04:14:35PM +, Jos?? Orlando Pereira wrote:
> Benjamin Arai wrote:
> > Is there a way to give priorities to queries or users? Something similar to
> > NICE in Linux. My goal is to give the updating (backend) application a very
> > low priority and give the web applicati
On Thu, Feb 22, 2007 at 07:59:35AM +, Gregory Stark wrote:
> "Gavin Sherry" <[EMAIL PROTECTED]> writes:
>
> > On Thu, 22 Feb 2007, Gregory Stark wrote:
> >
> >> But in a simple recursive tree search you have a node which wants to do a
> >> join
> >> between the output of tree level n against
> Moreover work on things like bitmapped indexes that other people want to help
> on is hampered by this need to be mailing around patches. If two or three
> people submit changes (based possibly on different old versions of the patch)
> the main developer has to merge them into his version of the
Chris Browne wrote:
> The trouble is that there needs to be a sufficient plurality in favor
> of *a particular move onwards* in order for it to happen.
>
> Right now, what we see is:
>
> - Some that are fine with status quo
> - Some that are keen on Subversion
> - Others keen on Monotone
> - Others
Yes, but if it was '2004-01-02 01:00:00'-'2004-01-01 00:00:00' it should
return 25:00:00, not 1 day 1:00.
I agree with Tom that this should be changed; I'm just arguing that we
might well need a backwards-compatibility solution for a while. At the
very least we'd need to make this change very clea
Jim C. Nasby wrote:
> On Thu, Feb 22, 2007 at 10:32:44PM -0500, Matthew T. O'Connor wrote:
> > I'm not sure this is a great idea, but I don't see how this would result
> > in large numbers of workers working in one database. If workers work
> > on tables in size order, and exit as soon as they
Jim C. Nasby wrote:
> On Fri, Feb 23, 2007 at 02:09:55PM +, Simon Riggs wrote:
> > > If you really want an interim solution, what about a builtin function
> > > that would explicitly mutate the definition and table contents (if any)
> > > along the lines you want? (assuming that's lots less w
On Fri, Feb 23, 2007 at 02:09:55PM +, Simon Riggs wrote:
> > If you really want an interim solution, what about a builtin function
> > that would explicitly mutate the definition and table contents (if any)
> > along the lines you want? (assuming that's lots less work than just
> > doing the
Osprey is a NetBSD running on m68k
http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=osprey&dt=2007-02-22%2023:00:18
It dumped core running VACUUM:
--- 1,5
VACUUM;
! server closed the connection unexpectedly
! This probably means the server terminated abnormally
! before
Warren Turkal wrote:
> On Thursday 22 February 2007 20:39, Alvaro Herrera wrote:
> > > Git is also pretty cool, too. You can even present a CVS interface on a
> > > git repository. That might address the build farm issue.
> >
> > But it wasn't portable, last time I checked.
>
> Git is in the FreeB
Tom Lane wrote:
Alvaro Herrera <[EMAIL PROTECTED]> writes:
I think you should increase pg_control version.
And the WAL page-header version, since this also changes WAL contents.
Here is an updated version. I've incremeted XLOG_PAGE_MAGIC and
PG_CONTROL_VERSION by one.
greetings, Florian Pfl
[EMAIL PROTECTED] (Richard Levitte - VMS Whacker) writes:
> In message <[EMAIL PROTECTED]> on Thu, 22 Feb 2007 17:38:26 +0100, Markus
> Schiltknecht <[EMAIL PROTECTED]> said:
>
> markus> > So far, I'm getting the sense that there are a lot of
> markus> > opinions on what replacement system to use,
"Simon Riggs" <[EMAIL PROTECTED]> writes:
> If this is standards-breaking as you say, I would withdraw immediately.
> I checked the SQL standard and could not see how this would do so. The
> standard states SELECT * would return columns in order; it doesn't say
> what that order should be, nor does
[EMAIL PROTECTED] wrote:
> On Fri, Feb 23, 2007 at 10:42:13AM -0300, Alvaro Herrera wrote:
> > Richard Levitte - VMS Whacker wrote:
> > > In message <[EMAIL PROTECTED]> on Fri, 23 Feb 2007 07:57:53 +0100, Markus
> > > Schiltknecht <[EMAIL PROTECTED]> said:
> > >
> > > markus> Uh, yah. But I was r
On Fri, 2007-02-23 at 07:52 -0500, Andrew Dunstan wrote:
> I really don't think that we can accept under any circumstances a
> situation where something ... breaks:
Yes, I've accepted that, in response to Peter earlier today.
> If you really want an interim solution, what about a builtin functi
Richard Levitte - VMS Whacker wrote:
> In message <[EMAIL PROTECTED]> on Fri, 23 Feb 2007 07:57:53 +0100, Markus
> Schiltknecht <[EMAIL PROTECTED]> said:
>
> markus> Uh, yah. But I was refering to the "lots of opinions on what
> markus> replacement system to use". This has not much to do with the
Simon Riggs wrote:
On Fri, 2007-02-23 at 11:25 +0100, Peter Eisentraut wrote:
Am Freitag, 23. Februar 2007 09:08 schrieb Simon Riggs:
If this is standards-breaking as you say, I would withdraw immediately.
I checked the SQL standard and could not see how this would do so. The
standard s
Am Freitag, 23. Februar 2007 12:25 schrieb Simon Riggs:
> My reading was that this was about constraints on columns, not the
> columns themselves, when that phrase was taken in context. I take it you
> think that reading was wrong?
I see nothing there that speaks of constraints.
--
Peter Eisentr
Vishal Arora wrote:
I would like to know how the data is been read from WAL file. If anyone
can help me with the WAL file structure. What are the basic functions
used by a pg_restore call.
pg_restore has nothing to do with WAL.
AFAIK the best description of the WAL file structure is in the co
On Fri, 2007-02-23 at 11:25 +0100, Peter Eisentraut wrote:
> Am Freitag, 23. Februar 2007 09:08 schrieb Simon Riggs:
> > If this is standards-breaking as you say, I would withdraw immediately.
> > I checked the SQL standard and could not see how this would do so. The
> > standard states SELECT * wo
Hi,
I would like to know how the data is been read from WAL file. If anyone can
help me with the WAL file structure. What are the basic functions used by a
pg_restore call.
Thanks
Visahal
_
With tax season right around the corner
Am Freitag, 23. Februar 2007 09:08 schrieb Simon Riggs:
> If this is standards-breaking as you say, I would withdraw immediately.
> I checked the SQL standard and could not see how this would do so. The
> standard states SELECT * would return columns in order; it doesn't say
> what that order shoul
Am Donnerstag, 22. Februar 2007 14:33 schrieb Teodor Sigaev:
> \df says only types of arguments, not a meaning.
Only if you don't provide argument names.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 9:
Am Donnerstag, 22. Februar 2007 18:07 schrieb Markus Schiltknecht:
> > I agree so enhancing parser oabout not standard construct isn't good.
>
> Generally? Wow! This would mean PostgreSQL would always lack behind
> other RDBSes, regarding ease of use. Please don't do that!
You are confusing making
On 2/23/07, Simon Riggs <[EMAIL PROTECTED]> wrote:
I had read that Phil had declined to work on it further; I hope he
changes his mind on that.
IIRC he just said he wasn't interested to work on the visible ordering
part (as in MySQL) and I don't think it's a problem as even if it's
related it's
Simon Riggs wrote:
>>> I propose that at CREATE TABLE time, the column ordering is
re-ordered
>>> so that the table columns are packed more efficiently. This would be
a
>>> physical re-ordering, so that SELECT * and COPY without explicit
column
>>> definitions would differ from the original CREATE
1 - 100 of 107 matches
Mail list logo
