Claudio Natoli wrote:
Hi all,
just a small note to anyone who is interested in the status of this port.
Firstly, the fork/exec changes are coming along well. The first patch, for
fork/exec'ing of backends has been accepted and applied. A second patch, for
fork/exec'ing of the remainder
Are we going to regenerate the 7.4.1 tar ball?
--
Tatsuo Ishii
Peter Eisentraut - PostgreSQL wrote:
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 03/12/21 17:36:34
Modified files:
doc/src/sgml : Tag: REL7_4_STABLE release.sgml
Hi,
I need to write a tab separated text file such that the first row contains
number of records in the table.
I insert first row with '0' (zero) as first column rest columns NULL.
Then at the end of writing records to table I do a select into Variable
count(*) from table.
update the first
Bruce Momjian wrote:
* a workable pipe replacement
I don't have 'pipe' mentioned on the win32 patch. Can you
give details?
Yeah you do. The second point under Problems with select().
Basically, the Win32 call to pipe() returns a file descriptor which is
invalid to pass on to Win32
On Mon, Dec 22, 2003 at 10:35:08AM -, Paul Punett wrote:
I need to write a tab separated text file such that the first row contains
number of records in the table.
Whether COPY does what you want may depend on what you want to do with
special characters. If your table contains strings
Tatsuo Ishii [EMAIL PROTECTED] writes:
Are we going to regenerate the 7.4.1 tar ball?
No. There is no difference other than some trailing spaces between
what Bruce committed and what I put in yesterday.
(It might be good if we had a more standardized way of generating
HISTORY though. I tried
Paul Punett [EMAIL PROTECTED] writes:
I need count as the first record? Any suggestions please ?
SQL does not guarantee any particular ordering of rows in a table.
You cannot do what you're doing and expect it to be reliable.
You could do something like this: add a sequence-number column to
On Mon, 22 Dec 2003, Tom Lane wrote:
Tatsuo Ishii [EMAIL PROTECTED] writes:
Are we going to regenerate the 7.4.1 tar ball?
No. There is no difference other than some trailing spaces between
what Bruce committed and what I put in yesterday.
(It might be good if we had a more standardized
SELECT x, y
(SELECT 1 AS ord, COUNT(*) as x, NULL AS y FROM tablex
UNION
SELECT 2, x, y FROM tablex)
May be you will have to do some explicit casting depending on the field
types.
--
Paulo Scardine
- Original Message -
From: Paul Punett [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent:
Marc G. Fournier [EMAIL PROTECTED] writes:
On Mon, 22 Dec 2003, Tom Lane wrote:
(It might be good if we had a more standardized way of generating
HISTORY though. I tried a couple different versions of lynx and
got a couple different outputs, none perfectly matching whatever
version Bruce is
Tom Lane wrote:
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
The thing is, if you drop a column that is used in a normal index, yes
the index is now useless - drop it.
However, since you can have (and I have) indexes like this:
CREATE INDEX asdf ON table (a, b, c) WHERE d IS NOT NULL;
If
Andreas Pflug [EMAIL PROTECTED] writes:
In that sample mentioned the index might be used mostly with a,b
columns. Dropping the index silently might damage the application
because it relies on an (a,b) index to be present. IMHO only Indexes
that span that single column should be dropped
On Mon, 2003-12-22 at 10:55, Tom Lane wrote:
Andreas Pflug [EMAIL PROTECTED] writes:
In that sample mentioned the index might be used mostly with a,b
columns. Dropping the index silently might damage the application
because it relies on an (a,b) index to be present. IMHO only Indexes
On Fri, 19 Dec 2003, Bruce Momjian wrote:
Robert Treat wrote:
Wasn't there a patch posted many months ago for PITR. IIRC it wasn't
complete, but would be a good starting point for those interested in
helping out. If it's in the archives it would be nice to add a link to
it on the project
Rod Taylor [EMAIL PROTECTED] writes:
I think Andreas is trying to argue that if you drop column b from index
(a, b) that the index should be converted into index(a) -- assuming of
course there isn't already an index(a).
That seems to be well outside the charter of DROP CASCADE. I think we
Tom Lane wrote:
Rod Taylor [EMAIL PROTECTED] writes:
I think Andreas is trying to argue that if you drop column b from index
(a, b) that the index should be converted into index(a) -- assuming of
course there isn't already an index(a).
That seems to be well outside the charter of DROP
Title: Postgres respond after toomany times to a query view
Hi, I developing a program using postgres and linux like operating system. My problem is this:
I have a quite complicated view with roughly 1 record. When I execute a simple query like this
select * from myview
postgres respond
I would like to mention that I am on MacOS 10.3 and have this issue
when compiling PHP with both iODBC support and Postgres support at
the same time.
I have to specify the -I/usr/include and the
-I/usr/local/pgsql/include in order for the build scripts to run
correctly. the problem is that at
Dear All,
I am planning to commit my PhD work (Under NDSU.edu) to further develop
PostGreSQL so that it can emerge as a major player in the distributed
grid computing. Please send me if you have any suggestions ...
Sincerely
Syed Mamun Raihan
---(end of
Title: postgres does not respond to a query view of 1 records roughly
Hi, I developing a program usinn postgres and linux like system operation. My problem is this:
I have a view quite complicated with roughly 1 record. When I execute a simple query like this
select * from myview
Hi,
I use PgSql for a lot of our company's need and I lack some features.
I would like to know if there is plans to implement:
- User permissions based on columns? (Ex: User1 has Select on Column CompayName
but User2 has update on column CompanyName while User3 has create new row
on table).
-
Title: Postgres respond after toomany times to a query view
It wouldhelp us to help you if you posted the view, tables involved
and indexes on those table. Also things like some of the postgresql.conf
parameters would help. Things like "effective_cache_size",
"sort_mem". Also how often the
Tom Lane wrote:
Tatsuo Ishii [EMAIL PROTECTED] writes:
Are we going to regenerate the 7.4.1 tar ball?
No. There is no difference other than some trailing spaces between
what Bruce committed and what I put in yesterday.
(It might be good if we had a more standardized way of generating
Tom Lane wrote:
Marc G. Fournier [EMAIL PROTECTED] writes:
On Mon, 22 Dec 2003, Tom Lane wrote:
(It might be good if we had a more standardized way of generating
HISTORY though. I tried a couple different versions of lynx and
got a couple different outputs, none perfectly matching
scott.marlowe wrote:
On Fri, 19 Dec 2003, Bruce Momjian wrote:
Robert Treat wrote:
Wasn't there a patch posted many months ago for PITR. IIRC it wasn't
complete, but would be a good starting point for those interested in
helping out. If it's in the archives it would be nice to add a
I'd rather pay the high fees and actually have access to the money ...
Paypal I'm 110% *against* ... they have had *way* too many problems. In
fact, there was a time when we ourselves setup the whole paypal account
and were looking at moving to it, until our clients started telling us
they
On Mon, Dec 22, 2003 at 12:17:32PM -0500, Bruce Momjian wrote:
The only problem with removing HISTORY from CVS is that we will not have
an easily reable list of release changes _until_ we package the release.
Perhaps we should keep HISTORY in CVS, but regenerate it on tarball
packaging, and
On Mon, 22 Dec 2003, Bruce Momjian wrote:
The only problem with removing HISTORY from CVS is that we will not have
an easily reable list of release changes _until_ we package the release.
Perhaps we should keep HISTORY in CVS, but regenerate it on tarball
packaging, and INSTALL too.
Confused
Marc G. Fournier wrote:
On Mon, 22 Dec 2003, Bruce Momjian wrote:
The only problem with removing HISTORY from CVS is that we will not have
an easily reable list of release changes _until_ we package the release.
Perhaps we should keep HISTORY in CVS, but regenerate it on tarball
Alvaro Herrera wrote:
On Mon, Dec 22, 2003 at 12:17:32PM -0500, Bruce Momjian wrote:
The only problem with removing HISTORY from CVS is that we will not have
an easily reable list of release changes _until_ we package the release.
Perhaps we should keep HISTORY in CVS, but regenerate it
On Mon, 22 Dec 2003, Bruce Momjian wrote:
Marc G. Fournier wrote:
On Mon, 22 Dec 2003, Bruce Momjian wrote:
The only problem with removing HISTORY from CVS is that we will not have
an easily reable list of release changes _until_ we package the release.
Perhaps we should keep
On Mon, 22 Dec 2003, Bruce Momjian wrote:
Alvaro Herrera wrote:
On Mon, Dec 22, 2003 at 12:17:32PM -0500, Bruce Momjian wrote:
The only problem with removing HISTORY from CVS is that we will not have
an easily reable list of release changes _until_ we package the release.
Perhaps we
Marc G. Fournier wrote:
On Mon, 22 Dec 2003, Bruce Momjian wrote:
Marc G. Fournier wrote:
On Mon, 22 Dec 2003, Bruce Momjian wrote:
The only problem with removing HISTORY from CVS is that we will not have
an easily reable list of release changes _until_ we package the release.
Marc G. Fournier wrote:
On Mon, 22 Dec 2003, Bruce Momjian wrote:
Alvaro Herrera wrote:
On Mon, Dec 22, 2003 at 12:17:32PM -0500, Bruce Momjian wrote:
The only problem with removing HISTORY from CVS is that we will not have
an easily reable list of release changes _until_ we
On Mon, 22 Dec 2003, Bruce Momjian wrote:
The only problem with removing HISTORY from CVS is that we will not have
an easily reable list of release changes _until_ we package the release.
Nonsense. Point 'em to
http://developer.postgresql.org/docs/postgres/release.html
Perhaps we should
Tom Lane wrote:
Marc G. Fournier [EMAIL PROTECTED] writes:
Confused here, but how up to date is HISTORY in CVS to start with?
One reason it's not is the confusion over which version is the master.
Last cycle, Peter encouraged people to add quick-and-dirty release notes
into release.sgml
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
Tom Lane said:
On an implementation level, where are you thinking of enforcing this?
Without digging deeply at all I thought probably in the postmaster.
Nah, that's a nonstarter, because the postmaster has basically
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
Last cycle, Peter encouraged people to add quick-and-dirty release notes
into release.sgml when important changes are made, and I thought that
worked pretty well.
Would you be more specific? How did it work well?
There was a place for
38 matches
Mail list logo
