Hi,
On Fri, Jan 18, 2013 at 12:48 AM, Dave Page wrote:
> Hi
>
>
>
> On Thu, Jan 17, 2013 at 2:56 AM, Lubomir Petrov
> wrote:
> > On Wed, Jan 16, 2013 at 8:56 AM, Dave Page wrote:
> >>
> >> Hi
> >>
> >> On Fri, Jan 11, 2013 at 7:31 PM, lpetrov wrote:
> >> > Hi all,
> >> >
> >> > I have identif
Hi
On Thu, Jan 17, 2013 at 2:56 AM, Lubomir Petrov wrote:
> On Wed, Jan 16, 2013 at 8:56 AM, Dave Page wrote:
>>
>> Hi
>>
>> On Fri, Jan 11, 2013 at 7:31 PM, lpetrov wrote:
>> > Hi all,
>> >
>> > I have identified a bug in handling Greenplum partitions SQL in
>> > pgAdmin3.
>> > The bug is vi
On Wed, Jan 16, 2013 at 8:56 AM, Dave Page wrote:
> Hi
>
> On Fri, Jan 11, 2013 at 7:31 PM, lpetrov wrote:
> > Hi all,
> >
> > I have identified a bug in handling Greenplum partitions SQL in pgAdmin3.
> > The bug is visible when clicking on Greenplum partition table (the
> partition
> > itself)
Hi
On Fri, Jan 11, 2013 at 7:31 PM, lpetrov wrote:
> Hi all,
>
> I have identified a bug in handling Greenplum partitions SQL in pgAdmin3.
> The bug is visible when clicking on Greenplum partition table (the partition
> itself) and then the SQL for the table is displayed in the SQL pane on the
>
Hi all,
I have identified a bug in handling Greenplum partitions SQL in
pgAdmin3. The bug is visible when clicking on Greenplum partition
table (the partition itself) and then the SQL for the table is
displayed in the SQL pane on the right. The SQL for partitions
represents randomly some
