Messages posted by: ashaar1

No, it should go to public schema if it is created like this. Unless you have changed the search_path variable.

It will be great if you can send me a screen shot fro pgAdmin 3, where you are able to browse the table etc. and also the command that you are using to do the select on the table using psql.

Are you prefixing the table names with schema name, in case you have created these tables in a non public schema. e.g.
psql -d postgres -U postgres
\c demo
\d sample.dept
select * from sample.dept;

You can find the information about the dotnet connector at the following link.

http://www.enterprisedb.com/documentation/8.2/dotnetdataprovider.html

I think you are using advanced server, since I can see the Oracle Compatibility Syntax.

See http://www.enterprisedb.com/downloads.do for EnterpriseDB Advanced Server related documentation.

For connecting to the database you can try the following syntax.

\c database-name

Rich,

In order to get pltcl.so you will need to compile the postgres code using --with-tcl configure switch. pltcl does not compile by default with postgres.

Execute command "POSTGRES/SRC/DIR/configure --help" to see information about rest of the configure options.

Thanks,
Ashaar

Hi Usama,

We have seen this issue mostly on Ubuntu 7.10 and openSUSE 10.3. We have a fix available for this in the latest version of the installers, planned for release in a weeks time.

In the mean time you can export the following variable before launching pgAdmin to make this work

export G_SLICE=always-malloc

You can try EnterpriseDB Postgres 8.3, which went GA a few days back. I think this issue is resolved in the 8.3 GA version.

The installers are available at http://postgres.enterprisedb.com/download.do

This is an issue with any java application executed on the latest version of X. We are awaiting a fix for this issue in the latest jre. As soon as it is release, FC8 should become a supported platform.

Thank you for using EnterpriseDb Postgres Installers. I will update this post as soon as we have a resolution.

Hi znmeb,

It will be great if you can come up with a tutorial that sets up everything as you have explained. It would be good starting point for an ROR Stack based installer.

To see the format of tutorials please go to our tutorials site at http://tutorials.enterprisedb.com

Thanks,
Ashaar

Hi Jon,

We are working towards making the suggested changes. Thank you for informing us about this issue.

postgres.enterprisedb.com is our Postgres Resource Center. We distribute community releases of postgres and its tools from this site.

You can get the EnterpriseDB Advanced Server downloads from www.enterprisedb.com/downlaods.do.

We have some tutorials available at http://tutorials.enterprisedb.com. These were written for windows and linux platforms but might still be helpful.

The Windows binaries work across both 32 and 64 bit platforms.

The initial snapshot does not require slon processes up and running on the slaves node, however for incremental changes each slave node should have its slon process running. It appears that in your case the slon process are not started on the slave nodes. If these processes are running but not replicating, you might have to share your log files so we can analyze and suggest the course of action.

The default replication interval is 10sec you can change it through conf files if required.

Please also glance through the pgAdmin3 documentation, it has built-in support for Slony-I replication.

Here is a sample master.conf file.

The conf file basically contains some configuration parameters for a cluster node slon process.

You may need to update the database connection parameters based on you system configuration.

# Sets how many cleanup cycles to run before a vacuum is done.
# Range: [0,100], default: 3
#vac_frequency=3

# Debug log level (higher value ==> more output).  Range: [0,4], default 0
#log_level=0

# Check for updates at least this often in milliseconds.
# Range: [10-60000], default 100
#sync_interval=100

# Maximum amount of time in milliseconds before issuing a SYNC event, 
# This prevents a possible race condition in which the action sequence 
# is bumped by the trigger while inserting the log row, which makes 
# this bump is immediately visible to the sync thread, but 
# the resulting log rows are not visible yet.  If the sync is picked 
# up by the subscriber, processed and finished before the transaction 
# commits, this transaction's changes will not be replicated until the 
# next SYNC.  But if all application activity suddenly stops, 
# there will be no more sequence bumps, so the high frequent -s check 
# won't detect that.  Thus, the need for sync_interval_timeout.
# Range: [0-120000], default 1000
#sync_interval_timeout=1000

# Maximum number of SYNC events to group together when/if a subscriber
# falls behind.  SYNCs are batched only if there are that many available 
# and if they are contiguous. Every other event type in between leads to 
# a smaller batch.  And if there is only one SYNC available, even -g60 
# will apply just that one. As soon as a subscriber catches up, it will
# apply every single SYNC by itself.
# Range:  [0,100], default: 6
#sync_group_maxsize=6

# If this parameter is 1, messages go both to syslog and the standard 
# output. A value of 2 sends output only to syslog (some messages will 
# still go to the standard output/error).  The default is 0, which means 
# syslog is off.  
# Range:  [0-2], default: 0
#syslog=0

# If true, include the process ID on each log line.  Default is false.
#log_pid=false

# If true, include the timestamp on each log line.  Default is true.
#log_timestamp=true

# A strftime()-conformant format string for use with log timestamps.
# Default is '%Y-%m-%d %H:%M:%S %Z'
#log_timestamp_format='%Y-%m-%d %H:%M:%S %Z'

# Where to write the pid file.  Default:  no pid file
#pid_file='/path/to/your/pidfile'

# Sets the syslog "facility" to be used when syslog enabled.  Valid 
# values are LOCAL0, LOCAL1, LOCAL2, LOCAL3, LOCAL4, LOCAL5, LOCAL6, LOCAL7.
#syslog_facility=LOCAL0

# Set the clsuter name that this instance of slon is running against
# default is to read it off the command line
cluster_name='slony_sample'

# Set slon's connection info, default is to read it off the command line
conn_info='dbname=postgres host=localhost port=5432 user=postgres'

# maximum time planned for grouped SYNCs
# If replication is behind, slon will try to increase numbers of
# syncs done targetting that they should take this quantity of
# time to process. in ms
# Range [10000,600000], default 60000. 
#desired_sync_time=60000

# Execute the following SQL on each node at slon connect time
# useful to set logging levels, or to tune the planner/memory
# settings.  You can specify multiple statements by seperating
# them with a ;
#sql_on_connection="SET log_min_duration_statement TO '1000';"

I am glad that you found the required information from the documentation. Please feel free to use the forums if you have any more questions.

EnterpriseDB Postgres 8.3 is now available on Mac OS X (i386 and PPC). Please visit the downloads page to get the binaries and see the release notes for this build.

http://postgres.enterprisedb.com/download.do

EnterpriseDB Postgres 8.2 Build 5 is now available for download.

This build contains the latest version of Postgres 8.2 (8.2.6). The installer has also been modified, now you can upgrade the build without having to uninstall and then re-install.

Please read the Release Notes for 8.2 Build 5, available on the downloads page, for more details.

EnterpriseDB Postgres 8.3 (8.3.0) is now available. Please get the latest installers from

http://postgres.enterprisedb.com/download.do

The core features of this build are:
1. PG 8.3.0
2. pgAdmin III 1.8.2
3. JDBC 8.3-603
4. ODBC 0080.0030.0010
5. PostGIS 1.3.2

The release notes for this release are also available on the downloads page.

We do not have a tutorial for this yet. If you would like to go ahead with it, we will try and extend all the help that we can.

IIRC you can do this by creating a new tablespace in the said location. Once this is created you would need to create a new database using this as its default tablespace.

Derek wrote:What is the different between Build 1 and Build 2 for Windows?

Windows Build 2 Installers contain the new Debugger Server module and the latest "MySQL to Postgres Migrator". Apart from these new modules some minor version upgrades of the existing modules are also part of the the latest release. Please see the Release Notes available on the download page for more details.

Linux 32 Build 2 Installers are now available, can you try out this issue on the new build.

This is the only documentation they have on their website as well.

Are there any specific questions? Please post them, we can try to help you out as much as we can.