Grokbase
Topics Posts Groups | in
x
[ help ]

Bruce Momjian (b...@momjian.us)

Profile | Posts (710)

User Information

Display Name:Bruce Momjian
Partial Email Address:b...@momjian.us
Posts:
710 total
25 in PostgreSQL - Admin
170 in PostgreSQL - Advocacy
1 in PostgreSQL - Announce
105 in PostgreSQL - Bugs
173 in PostgreSQL - Docs
182 in PostgreSQL - General
13 in PostgreSQL - Interfaces
21 in PostgreSQL - JDBC
3 in PostgreSQL - Novice
23 in PostgreSQL - Performance
8 in PostgreSQL - SQL

5 Most Recent

All Posts
1) Bruce Momjian Re: [GENERAL] Query output into a space delimited/location sensitive file
| +1 vote
Not possible --- many data types are of variable length.
PostgreSQL - General
[ Profile | Reply to group ] [ Flat  Thread  Threaded ]
Ubence Quevedo wrote:
> What would the command be to have a query result be put into a
> location/space sensitive file [position 1 through 5 would be one thing
> where position 6 through 10 would be the next field, 11 through 16
> another, etc]? Is this even possible with Postgres?

Not possible --- many data types are of variable length.

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [email protected: majo...@postgresql.org] so that your
message can get through to the mailing list cleanly
2) Bruce Momjian Re: [GENERAL] Pains in upgrading to 8.3
| +1 vote
Using the new pg_dump for dumping older versions during an ugprade is just inconvenient and...
PostgreSQL - General
[ Profile | Reply to group ] [ Flat  Thread  Threaded ]
Magnus Hagander wrote:
> Dave Page wrote:
> > On Fri, Feb 15, 2008 at 4:21 PM, Tony Caduto
> > <tony_caduto@amsoftwaredesign.com> wrote:
> >> paul rivers wrote:
> >>  >>
> >> > Going from 8.2.4 and 8.2.6 to 8.3.0 has been painless for me.
> >> > However, unlike the blogger you cite, I read the directions before,
> >>  > not after, attempting it.
> >>
> >>
> >> The blogger has a point about pg_dump and restore, it could be much
> >>  better, for example
> >> the backup process could be part of the server core and instead of
> >> having a fat client where most of the process is running on the client,
> >>  a API could be
> >> used where the backup is generated on the server and then have options
> >> where it could be left on the server or transferred to the clients PC.
> >
> > Not really an option - the reason it's recommended to use the new
> > pg_dump version with the older server when upgrading is to allow the
> > dump to be made in the way most compatible with the new server,
> > effectively doing some of the upgrade process as part of the dump
> > operation.
>
> For the case of upgrading, it wouldn't work. But there are certainly
> other cases where it would help. Say from your central pgadmin console
> administering 10 servers from 3 different major release trees :-(
>
> It can be done with commandline pg_dump, but it means you have to have
> three different installs on your management or backup or whatever
> machine. Those cases would certainly be easier if you could just call a
> backup API on the server that would feed you the data... (yes, there are
> ways to do it with ssh tunneling and whatever, but that's yet another
> external service that has to be set up and configured)

Using the new pg_dump for dumping older versions during an ugprade is
just inconvenient and something we should not need to do.  At the worst
we should have a way for us to upgrade the older version of pg_dump with
whatever functionality we need and just tell people to be running the
most recent minor release before upgrading.

What cases on the past have needed the new pg_dump?

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org/
3) Bruce Momjian Re: [pgsql-www] [GENERAL] end of life for pg versions...
| +1 vote
We could record the dates we made versions EOL and they can interpolate from there.
PostgreSQL - General
[ Profile | Reply to group ] [ Flat  Thread  Threaded ]
Tom Lane wrote:
> Robert Treat <xzilla@users.sourceforge.net> writes:
> > Of course we would still need to add an EOL page... I think one could make a
> > strong argument for a static url for EOL info now that windows is EOL for <
> > 8.2.
>
> You could make a strong argument for a page stating that versions
> thus-and-so are *already* EOL'd. What the OP seems to be insisting
> is that we produce a formal policy and timetable for future EOL
> decisions, neither of which seem very likely or desirable to me.

We could record the dates we made versions EOL and they can interpolate
from there.

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [email protected: majo...@postgresql.org] so that your
message can get through to the mailing list cleanly
4) Bruce Momjian Re: [GENERAL] hyperthreading and pqlib
| +1 vote
What version of Postgres? Does the application freeze or the operating system? We have not heard...
PostgreSQL - General
[ Profile | Reply to group ] [ Flat  Thread  Threaded ]
luca.ciciriello@email.it wrote:
> Hi all.
> Has someone encountered a problem using pqlib in a multi-threading
> application (POSIX or Win32) when the Intel Hyperthreading is enabled?
> Disabling the hyperthreading option from the bios of the computer all works
> fine, otherwise the threaded application does freeze randomically after a
> while (This behaviour is common to Linux and WIndows version of the
> multi-threaded application).Any idea?Thanks in advance.Luca.

What version of Postgres?  Does the application freeze or the operating
system?  We have not heard similar reports.  We don't actually recommend
hyperthreading usually.

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org/
5) Bruce Momjian Re: [GENERAL] postgresql book - practical or something newer?
| +1 vote
The good and bad news is that the best way to do things often changes from release to release,...
PostgreSQL - General
[ Profile | Reply to group ] [ Flat  Thread  Threaded ]
Tom Hart wrote:
> I definitely think that the lists are one of the shining stars for
> postgresql support. I've learned some good reference stuff from online
> docs/google but the really tricky questions were only answered here, and
> amazingly enough, quickly and with good humor. Perhaps what we really
> need is somebody to comb through the archives looking for common
> problems or exceptional solutions and compile them into a "book".

The good and bad news is that the best way to do things often changes
from release to release, hence the need to get the most current
information from the mailing lists.

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

spacer
Profile | Posts (710)
Home > People > Bruce Momjian
Grokbase | Groups | Tags | People | Add a group | FAQ | About

Provide feedback | del.icio.us | Credits | Created by John