Dennis Gearon wrote:
> I set up the same characteristics on the console, and it runs
> fine, (COPY commands will import back, right? That's what it output.)
>
> On the console, it was:
> pg_dump -vaF p -f dbase.sql -U user-name dbase-name
>
> More details:
> about 11 tables, practically emp
Hi, All
I read documentation
(http://www.postgresql.org/docs/8.4/interactive/runtime-config-resource.html)
and googled effective_io_concurrency but have not found any expanded
explanation of what it actually is. I feel it rater significant for PG
performance and would like to ask gurus to provide
Gerhard Wiesinger writes:
> On Sun, 18 Oct 2009, Tom Lane wrote:
>> The OFFSET bit is a kluge, but is needed to keep the planner from
>> flattening the subquery and undoing your work.
> Thnx Tom. It also works without the OFFSET kludge. Any ideas why?
Probably because you have the function decla
I have created a table where a unique row is defined by 5 columns and
have created an index on these 5 columns. If I then do a select with a
where clause that only consists of 3 of these columns, will I get the
speed benefits from the index that I have created, or will I need to
create another inde
"Bierbryer, Andrew" writes:
> I have created a table where a unique row is defined by 5 columns and
> have created an index on these 5 columns. If I then do a select with a
> where clause that only consists of 3 of these columns, will I get the
> speed benefits from the index that I have created,
On Mon, 19 Oct 2009, Sergey Konoplev wrote:
I feel it rater significant for PG performance and would like to ask
gurus to provide some more description here.
It's probably not as significant as you are hoping. Currently the code
only kicks in when you're doing a Bitmap Heap Scan, which is re
If you issue an immediate shutdown to the database, autovacumm will not
process tables that should be vacuumed until manually re-analyzed.
PG 8.3.8
Relevant settings:
autovacuum = on
log_autovacuum_min_duration = 0
autovacuum_max_workers = 3
autovacuum_naptime = 1min
autovacuum_vacuum
I am unable to restore data with the use of WAL files by following procedure.
I have done following changes in postgres.conf to enable WAL archiving...
archive_mode = on # allows archiving to be done
archive_command = 'copy "%p" "C:\\archivedir\\%f"'
I have one database(buil
I'm using 8.2.4
Numeric with scale precision always shows the trailing zeros.
Numeric plain only shows numbers after the decimal point that are being
used.
I would like to have the data in my table with scale and precision, but
my views to be cast to numeric without any scale or precision.
Ho
Brad Nicholson writes:
> If you issue an immediate shutdown to the database, autovacumm will not
> process tables that should be vacuumed until manually re-analyzed.
AFAICS this is an unsurprising consequence of flushing stats on a crash.
If you don't like it, avoid immediate shutdowns --- they a
Sim Zacks writes:
> Numeric with scale precision always shows the trailing zeros.
> Numeric plain only shows numbers after the decimal point that are being
> used.
That statement is false:
regression=# select 1234.000::numeric;
numeric
--
1234.000
(1 row)
I'm not sure offhand what i
On Mon, 2009-10-19 at 12:07 -0400, Tom Lane wrote:
> Brad Nicholson writes:
> > If you issue an immediate shutdown to the database, autovacumm will not
> > process tables that should be vacuumed until manually re-analyzed.
>
> AFAICS this is an unsurprising consequence of flushing stats on a cras
Brad Nicholson writes:
> On Mon, 2009-10-19 at 12:07 -0400, Tom Lane wrote:
>> That seems like a fundamentally stupid idea, unless you are unconcerned
>> with the time and cost of getting the DB running again, which seemingly
>> you are.
> I disagree that this is fundamentally stupid. We are tal
On Mon, Oct 19, 2009 at 10:44 AM, Tom Lane wrote:
> Brad Nicholson writes:
>> On Mon, 2009-10-19 at 12:07 -0400, Tom Lane wrote:
>>> That seems like a fundamentally stupid idea, unless you are unconcerned
>>> with the time and cost of getting the DB running again, which seemingly
>>> you are.
>
>
On Mon, 2009-10-19 at 10:53 -0600, Scott Marlowe wrote:
> On Mon, Oct 19, 2009 at 10:44 AM, Tom Lane wrote:
> > Brad Nicholson writes:
> >> On Mon, 2009-10-19 at 12:07 -0400, Tom Lane wrote:
> >>> That seems like a fundamentally stupid idea, unless you are unconcerned
> >>> with the time and cost
On Mon, Oct 19, 2009 at 11:06 AM, Brad Nicholson
wrote:
> On Mon, 2009-10-19 at 10:53 -0600, Scott Marlowe wrote:
>> On Mon, Oct 19, 2009 at 10:44 AM, Tom Lane wrote:
>> > Brad Nicholson writes:
>> >> On Mon, 2009-10-19 at 12:07 -0400, Tom Lane wrote:
>> >>> That seems like a fundamentally stupi
On Mon, 2009-10-19 at 11:16 -0600, Scott Marlowe wrote:
> On Mon, Oct 19, 2009 at 11:06 AM, Brad Nicholson
> wrote:
> > On Mon, 2009-10-19 at 10:53 -0600, Scott Marlowe wrote:
> >> On Mon, Oct 19, 2009 at 10:44 AM, Tom Lane wrote:
> >> > Brad Nicholson writes:
> >> >> On Mon, 2009-10-19 at 12:07
Scott Marlowe writes:
> All of this is completely besides the point that a database that's
> been shutdown immediately / had the power cord yanked comes back up
> and doesn't start autovacuuming automatically, which seems a
> non-optimal behaviour.
It'll start as soon as you've modified enough ro
On Mon, 19 Oct 2009, Tom Lane wrote:
Gerhard Wiesinger writes:
On Sun, 18 Oct 2009, Tom Lane wrote:
The OFFSET bit is a kluge, but is needed to keep the planner from
flattening the subquery and undoing your work.
Thnx Tom. It also works without the OFFSET kludge. Any ideas why?
Probably
On Oct 19, 2009, at 10:49 AM, Gerhard Wiesinger wrote:
None of the function is declared VOLATILE. Any other idea?
If they are not declared with a volatility category at all, the
default is VOLATILE. Is that a possibility?
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-g
Gerhard Wiesinger writes:
> On Mon, 19 Oct 2009, Tom Lane wrote:
>> Probably because you have the function declared VOLATILE.
> None of the function is declared VOLATILE. Any other idea?
[ shrug... ] There are other possible reasons why the planner would
fail to flatten a subquery, but none of
On Mon, Oct 19, 2009 at 11:27 AM, Tom Lane wrote:
> Scott Marlowe writes:
>> All of this is completely besides the point that a database that's
>> been shutdown immediately / had the power cord yanked comes back up
>> and doesn't start autovacuuming automatically, which seems a
>> non-optimal beh
On Oct 19, 2009, at 11:26 AM, Scott Marlowe wrote:
That could be a pretty bad worst case scenario for certain types of
tables / usage patterns.
Given that (presumably) the database server is not failing repeatedly
without some kind of operator notification, isn't it at least somewhat
reaso
On Mon, 2009-10-19 at 11:35 -0700, Christophe Pettus wrote:
> On Oct 19, 2009, at 11:26 AM, Scott Marlowe wrote:
> > That could be a pretty bad worst case scenario for certain types of
> > tables / usage patterns.
>
> Given that (presumably) the database server is not failing repeatedly
> withou
Brad Nicholson writes:
> autoanalyze will automatically analyze new tables when they don't have
> stats. It seems logical that it should handle this case where the table
> also does not have stats.
It will autoanalyze once a sufficient number of inserts have occurred.
The effect of a crash is ju
On Mon, 2009-10-19 at 15:01 -0400, Tom Lane wrote:
> Brad Nicholson writes:
> > autoanalyze will automatically analyze new tables when they don't have
> > stats. It seems logical that it should handle this case where the table
> > also does not have stats.
>
> It will autoanalyze once a sufficie
On Mon, 2009-10-19 at 15:09 -0400, Brad Nicholson wrote:
> On Mon, 2009-10-19 at 15:01 -0400, Tom Lane wrote:
> > Brad Nicholson writes:
> > > autoanalyze will automatically analyze new tables when they don't have
> > > stats. It seems logical that it should handle this case where the table
> > >
Hi,
I'am searching for a free tool to design a Postgre Database. There is
something similar to MySQL Workbench?
Best Regards,
Andre.
Brad Nicholson writes:
> What about the question that Scott and I both asked - what about query
> plans. Will they be affected?
No, they should be the same as what you were getting just before the
crash. The planner only looks at pg_statistic which is a whole
different thing.
On Mon, Oct 19, 2009 at 7:12 PM, Greg Smith wrote:
> On Mon, 19 Oct 2009, Sergey Konoplev wrote:
>
>> I feel it rater significant for PG performance and would like to ask gurus
>> to provide some more description here.
>
> It's probably not as significant as you are hoping. Currently the code onl
On Mon, Oct 19, 2009 at 2:18 PM, Andre Lopes wrote:
> Hi,
>
> I'am searching for a free tool to design a Postgre Database. There is
> something similar to MySQL Workbench?
Search the archives this came up within the last couple of months. I
currently use Power Architect, it's a beta product and
I have a (large) corrupted 8.3.7 database that I'd like to fix.
It has this problem :
pg_dump: SQL command failed
pg_dump: Error message from server: ERROR: missing chunk number 2 for toast
value 10114 in pg_toast_16426
I've seen this particular syndrome before and fixed it by deleting th
Greetings,
I find myself needing to regularly import data encoded as Mac OS Roman
(yes, it is coming from an Macintosh OS 9 system) into a UTF-8
PostgreSQL database. Any advice on how to do so, since Mac OS Roman
is (reasonably enough) not one of PG's standard character encodings?
Thanks
On Mon, Oct 19, 2009 at 02:54:38PM -0700, Christophe Pettus wrote:
> I find myself needing to regularly import data encoded as Mac OS Roman
> (yes, it is coming from an Macintosh OS 9 system) into a UTF-8
> PostgreSQL database.
How tightly integrated into PG do you want it? You can define cus
> I find myself needing to regularly import data encoded as Mac OS Roman
> (yes, it is coming from an Macintosh OS 9 system) into a UTF-8
> PostgreSQL database. Any advice on how to do so, since Mac OS Roman
> is (reasonably enough) not one of PG's standard character encodings?
Use iconv; it's a
Christophe Pettus writes:
> I find myself needing to regularly import data encoded as Mac OS Roman
> (yes, it is coming from an Macintosh OS 9 system) into a UTF-8
> PostgreSQL database. Any advice on how to do so, since Mac OS Roman
> is (reasonably enough) not one of PG's standard charact
> Maybe iconv knows about it?
On OS X it definitely does; on other platforms it may not since supported
encodings are platform-dependent.
--
Scott Ribe
scott_r...@killerbytes.com
http://www.killerbytes.com/
(303) 722-0567 voice
--
Sent via pgsql-general mailing list (pgsql-general@postgresql
On Oct 19, 2009, at 4:39 PM, Scott Ribe wrote:
On OS X it definitely does; on other platforms it may not since
supported
encodings are platform-dependent.
The Centos version knows about it as well; thanks, that's the perfect
solution.
--
-- Christophe Pettus
x...@thebuild.com
--
Sen
We have a system in which a large amount of the data is stored as large
objects now in PG 8.4. The relational aspects of these objects are
stored using traditional tables, but we store a lot of binary data
(files, images) and XML objects that are compressed and then encrypted.
The ACID proper
On Sun, Oct 18, 2009 at 12:00 PM, Raymond O'Donnell wrote:
> On 18/10/2009 11:30, Alban Hertroys wrote:
>
>> Short of enumerating those results in your application, the easiest
>> approach is probably to wrap your query in a join with generate_series
>> like so:
>>
>> SELECT a, s.b
>> FROM (
>>
On Mon, Oct 19, 2009 at 9:11 PM, David Wall wrote:
> We have a system in which a large amount of the data is stored as large
> objects now in PG 8.4. The relational aspects of these objects are stored
> using traditional tables, but we store a lot of binary data (files, images)
> and XML objects
Andre Lopes wrote:
Hi,
I'am searching for a free tool to design a Postgre Database. There is
something similar to MySQL Workbench?
Best Regards,
Andre.
From 9/11/2009 "Open source database design tool , alternative to
MicroOLDAP"
Open ModelSphere: http://www.modelsphere.org/
From 5/
On Mon, 2009-10-19 at 07:18 -0700, Mitesh51 wrote:
> I am unable to restore data with the use of WAL files by following procedure.
>
> I have done following changes in postgres.conf to enable WAL archiving...
>
> archive_mode = on # allows archiving to be done
> archive_command = 'cop
On Mon, 2009-10-19 at 07:18 -0700, Mitesh51 wrote:
> I am unable to restore data with the use of WAL files by following procedure.
>
> I have done following changes in postgres.conf to enable WAL archiving...
>
> archive_mode = on # allows archiving to be done
> archive_command = 'cop
Hi,
When I use ecpg code to download File from database, error occurred
occasionally as below:
“could not connect to server: Connection timed outIs the server running
on host "DB" and acceptingTCP/IP connections on port 5432?”
This my code:
conn = PQse
On Tue, 2009-10-20 at 12:12 +0800, 黄永卫 wrote:
>
> Oct 18 10:46:11 SUC02 postgres[10997]: [2-1] LOG: unexpected EOF on
> client connection
> Oct 18 10:46:11 SUC02 postgres[15899]: [2-1] LOG: could not receive
> data from client: Connection reset by peer
That looks a lot like lower-level networki
On Mon, Oct 19, 2009 at 10:48:47PM -0400, Guy Rouillier wrote:
> Andre Lopes wrote:
>> Hi,
>> I'am searching for a free tool to design a Postgre Database. There is
>> something similar to MySQL Workbench?
>> Best Regards,
>> Andre.
>
> From 9/11/2009 "Open source database design tool , alterna
Craig Ringer wrote:
On Tue, 2009-10-20 at 12:12 +0800, 黄永卫 wrote:
Oct 18 10:46:11 SUC02 postgres[10997]: [2-1] LOG: unexpected EOF on
client connection
Oct 18 10:46:11 SUC02 postgres[15899]: [2-1] LOG: could not receive
data from client: Connection reset by peer
That looks a lot like lower-l
Hi,
I second the request for the files refered to in the video --
particularly postgresql.conf.simple and dependencies.
Cheers,
Viktor
Christophe Pettus wrote:
> The video archive for the 10/13 SFPUG meeting, "The Mighty GUCS: A
> guide to the essential PostgreSQL settings you need to know," is
49 matches
Mail list logo
