Peter Eisentraut writes:
> We could fix this in several ways. Either hardcode exceptions for the
> 'html' directory in prep_buildtree, or only create directories that
> contain a makefile, which could also be achieved by pruning empty
> directories at the end of prep_buildtree. All of these migh
On tor, 2010-08-26 at 14:06 -0400, Tom Lane wrote:
> Peter Eisentraut writes:
> > We could fix this in several ways. Either hardcode exceptions for the
> > 'html' directory in prep_buildtree, or only create directories that
> > contain a makefile, which could also be achieved by pruning empty
> >
Peter Eisentraut writes:
> If you have "find" superpowers, maybe you can tell it not to process
> anything below doc/src/sgml/.
I just hardwired some rmdir's ;-). Pretty is not the goal right now.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgr
Excerpts from Peter Eisentraut's message of jue ago 26 14:25:31 -0400 2010:
> If you have "find" superpowers, maybe you can tell it not to process
> anything below doc/src/sgml/.
line 25:
find "$sourcetree" -type d \( -name CVS -prune -o -path "*doc/src/sgml/*"
-prune -o -print \)
--
Álvaro H
Alvaro Herrera writes:
> Excerpts from Peter Eisentraut's message of jue ago 26 14:25:31 -0400 2010:
>> If you have "find" superpowers, maybe you can tell it not to process
>> anything below doc/src/sgml/.
> line 25:
> find "$sourcetree" -type d \( -name CVS -prune -o -path "*doc/src/sgml/*"
>
Excerpts from Tom Lane's message of jue ago 26 16:38:07 -0400 2010:
> Alvaro Herrera writes:
> > Excerpts from Peter Eisentraut's message of jue ago 26 14:25:31 -0400 2010:
> >> If you have "find" superpowers, maybe you can tell it not to process
> >> anything below doc/src/sgml/.
>
> > line 25:
Excerpts from Alvaro Herrera's message of jue ago 26 16:46:42 -0400 2010:
> Excerpts from Tom Lane's message of jue ago 26 16:38:07 -0400 2010:
> > Alvaro Herrera writes:
> > > Excerpts from Peter Eisentraut's message of jue ago 26 14:25:31 -0400
> > > 2010:
> > >> If you have "find" superpowers,
The following bug has been logged online:
Bug reference: 5629
Logged by: Alexsander
Email address: alexsander.r...@gmail.com
PostgreSQL version: 8.3.11
Operating system: Linux
Description:ALTER SEQUENCE foo START execute a RESTART
Details:
Steps to reproduce:
CREAT
"Alexsander" writes:
> CREATE SEQUENCE foo;
> SELECT setval('foo',12345);
> ALTER SEQUENCE foo START WITH 10; -- can't change value
> SELECT nextval('foo'); -- it's 10 instead of 12346
> Apparently START is executing a RESTART.
Yup. That's what it's defined to do, pre-8.4.
Then the docs are misleading:
http://www.postgresql.org/docs/8.3/static/sql-altersequence.html
According the docs, 8.3 does NOT have a START clause -- only RESTART. I
think a START clause should raise an error at 8.3 servers; there's a chance
of someone run the command in several servers (like a p
Alexsander Rosa writes:
> According the docs, 8.3 does NOT have a START clause -- only RESTART. I
> think a START clause should raise an error at 8.3 servers; there's a chance
> of someone run the command in several servers (like a pgdiff) and get
> different behaviour for the same command.
We're
On 2010-08-27 12:51 AM +0300, Tom Lane wrote:
Alexsander Rosa writes:
According the docs, 8.3 does NOT have a START clause -- only RESTART. I
think a START clause should raise an error at 8.3 servers; there's a chance
of someone run the command in several servers (like a pgdiff) and get
differe
12 matches
Mail list logo
